From: Michael Forney <mforney@mforney.org>
To: 9front@9front.org
Subject: Re: [9front] USB isochronous endpoint with feedback
Date: Wed, 10 Feb 2021 12:55:57 -0800 [thread overview]
Message-ID: <CAGw6cBsUD_YuvVu72rswQ_7SKmD8c4eV9cj-HRLs4ekFWc8Opw@mail.gmail.com> (raw)
In-Reply-To: <3B1469EE2DD79F42095548A2DBAAD554@felloff.net>
On 2021-02-10, cinap_lenrek@felloff.net <cinap_lenrek@felloff.net> wrote:
> applied. you forgot to submit the patches for the header
> with the addition of isousage attribute and the constants.
>
> approximated it.
Hmm, I don't know what you mean. The patches look fine to me, and they
match what you committed except for some whitespace differences.
0002-nusb-record-iso-usage-in-endpoint.patch includes the changes to
lib/usb.h.
Anyway, thank you for applying!
prev parent reply other threads:[~2021-02-10 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 2:02 Michael Forney
2021-02-09 2:31 ` cinap_lenrek
2021-02-10 19:10 ` cinap_lenrek
2021-02-10 20:55 ` Michael Forney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGw6cBsUD_YuvVu72rswQ_7SKmD8c4eV9cj-HRLs4ekFWc8Opw@mail.gmail.com \
--to=mforney@mforney.org \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).