From: Sean Young <sean@mess.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Johan Hovold <johan@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
linux-media@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, Oliver Neukum <oneukum@suse.com>,
stable@vger.kernel.org, Dongliang Mu <mudongliangabcd@gmail.com>
Subject: Re: [PATCH RESEND] media: flexcop-usb: fix endpoint type check
Date: Thu, 22 Sep 2022 11:39:27 +0100 [thread overview]
Message-ID: <Yyw7X2KkabBpPvIo@gofer.mess.org> (raw)
In-Reply-To: <Yyw1CJgv6nreCtB9@kroah.com>
On Thu, Sep 22, 2022 at 12:12:24PM +0200, Greg Kroah-Hartman wrote:
> On Thu, Sep 22, 2022 at 11:37:36AM +0200, Johan Hovold wrote:
> > Thanks. These are the follow-up cleanups:
> >
> > https://lore.kernel.org/lkml/20220822151456.27178-1-johan@kernel.org/
>
> Thanks, I'll take them after the first one was merged into Linus's tree.
>
> > Perhaps we should start taking USB related changes like this through the
> > USB tree by default. Posting patches to the media subsystem feels like
> > shooting patches at a black hole.
>
> I agree, there's been a bunch of patches sent there (some with security
> fixes) that are not getting responded to :(
The patches were missed are all DVB related, which is Mauro's responsibility.
As far as I can see, other parts of the media subsystem are well looked after.
Sean
next prev parent reply other threads:[~2022-09-22 10:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 15:10 [PATCH RESEND] media: flexcop-usb: fix endpoint type check Johan Hovold
2022-09-20 9:00 ` Johan Hovold
2022-09-22 8:41 ` Greg Kroah-Hartman
2022-09-22 9:37 ` Johan Hovold
2022-09-22 10:12 ` Greg Kroah-Hartman
2022-09-22 10:39 ` Sean Young [this message]
2022-09-22 10:43 ` Greg Kroah-Hartman
2022-09-26 8:59 ` Greg Kroah-Hartman
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=Yyw7X2KkabBpPvIo@gofer.mess.org \
--to=sean@mess.org \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mudongliangabcd@gmail.com \
--cc=oneukum@suse.com \
--cc=stable@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