From: Maxim Devaev <mdevaev@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Felipe Balbi <balbi@kernel.org>,
sandeen@redhat.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: gadget: f_hid: idle uses the highest byte for duration
Date: Wed, 28 Jul 2021 09:48:39 +0300 [thread overview]
Message-ID: <20210728094839.23a185d8@reki> (raw)
In-Reply-To: <YQD8MfEZxPHYhnrz@kroah.com>
> Greg KH <gregkh@linuxfoundation.org> wrote:
> Argh, just missed me committing this. Thanks for the review, sorry it
> missed getting added to the final commit :(
No, it's my fault, I messed up the process and everything went wrong.
I will improve my interaction when working on the next patch.
Sorry again. Although I read the manual on working with kernel mailings,
I forgot about some things. Github PRs and all such things stupefy me :)
prev parent reply other threads:[~2021-07-28 6:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 18:58 [PATCH] usb: gadget: f_hid: idle uses the highest byte for duration Maxim Devaev
2021-07-28 6:25 ` Greg KH
2021-07-28 6:28 ` Maxim Devaev
2021-07-28 6:31 ` Felipe Balbi
2021-07-28 6:41 ` Greg KH
2021-07-28 6:47 ` Felipe Balbi
2021-07-28 6:48 ` Maxim Devaev [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=20210728094839.23a185d8@reki \
--to=mdevaev@gmail.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sandeen@redhat.com \
/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).