From: Pavel Hofman <pavel.hofman@ivitera.com>
To: John Keeping <john@metanate.com>
Cc: linux-usb@vger.kernel.org, Felipe Balbi <balbi@kernel.org>
Subject: Re: [PATCH] usb: gadget: u_audio: Fix high-speed max packet size
Date: Fri, 31 Jan 2020 13:47:29 +0100 [thread overview]
Message-ID: <2dfd0136-ebfd-102c-e944-0a04b405968e@ivitera.com> (raw)
In-Reply-To: <20200131112733.758ab77c.john@metanate.com>
Hi John,
>> I apologize for a basic question - please which official repository to
>> check status of a gadget patch after being accepted? Thanks a lot for
>> the information.
>
> If you have a kernel tree, you can ask the MAINTAINERS file:
>
> ./scripts/get_maintainer.pl --scm -f drivers/usb/gadget/function/u_audio.c
>
> I'd expect this to appear in Felipe's tree first at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
>
> but I don't see it yet. I guess it won't be picked up until after the
> merge window.
>
Thanks a lot for you info. How does the maintainer pick a patch from the
flood of messages? Some extra headers (Tested:by, Acked-by:) are sent
separately by different people, does the maintainer have to keep track
of all of that manually?
Thanks for your enlightenment.
Pavel.
next prev parent reply other threads:[~2020-01-31 12:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 7:29 USB:UAC2: Incorrect req->length > maxpacket*mc Pavel Hofman
2020-01-10 11:28 ` [PATCH] usb: gadget: f_uac2: fix packet size calculation John Keeping
2020-01-11 9:12 ` Pavel Hofman
2020-01-11 9:31 ` USB:UAC2: Incorrect req->length > maxpacket*mc - cause likely found Pavel Hofman
2020-01-11 9:49 ` Pavel Hofman
2020-01-14 18:39 ` Pavel Hofman
2020-01-14 20:04 ` John Keeping
2020-01-14 20:21 ` Pavel Hofman
2020-01-16 15:39 ` Pavel Hofman
2020-01-17 10:40 ` [PATCH] usb: gadget: u_audio: Fix high-speed max packet size John Keeping
2020-01-19 14:53 ` Pavel Hofman
2020-01-24 12:16 ` Pavel Hofman
2020-01-31 10:30 ` Pavel Hofman
2020-01-31 11:27 ` John Keeping
2020-01-31 12:47 ` Pavel Hofman [this message]
2020-01-31 13:09 ` Felipe Balbi
2020-01-24 12:52 ` Felipe Balbi
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=2dfd0136-ebfd-102c-e944-0a04b405968e@ivitera.com \
--to=pavel.hofman@ivitera.com \
--cc=balbi@kernel.org \
--cc=john@metanate.com \
--cc=linux-usb@vger.kernel.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).