All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linhaoguo86@gmail.com, mchehab@kernel.org, sean@mess.org,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] media: mceusb: Use new usb_control_msg_*() routines" failed to apply to 6.0-stable tree
Date: Wed, 26 Oct 2022 18:21:24 +0200	[thread overview]
Message-ID: <Y1lehL94Q8p4Dpkn@kroah.com> (raw)
In-Reply-To: <Y1lTk7Gn0XGdLfa7@rowland.harvard.edu>

On Wed, Oct 26, 2022 at 11:34:43AM -0400, Alan Stern wrote:
> On Wed, Oct 26, 2022 at 05:11:04PM +0200, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 6.0-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> > 
> > Possible dependencies:
> > 
> > 41fd1cb61514 ("media: mceusb: Use new usb_control_msg_*() routines")
> 
> Greg:
> 
> I can submit a patch for the -stable trees that fixes the problem 
> reported by syzbot without converting the mceusb driver to use the new 
> usb_control_msg_*() routines.  Would that be okay?  Or do you prefer 
> simply not to include this patch (which merely fixes a warning) in the 
> stable kernels?

If it's just a warning, no need to really worry about it.  But note that
the usb_control_msg_*() functions are in 5.10.y and newer kernels, so
maybe just do this using the real functions for 5.15 and 6.0?

thanks,

greg k-h

  reply	other threads:[~2022-10-26 16:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 15:11 FAILED: patch "[PATCH] media: mceusb: Use new usb_control_msg_*() routines" failed to apply to 6.0-stable tree gregkh
2022-10-26 15:34 ` Alan Stern
2022-10-26 16:21   ` Greg KH [this message]
2022-10-26 17:26     ` Alan Stern
2022-10-26 17:34       ` Greg KH

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=Y1lehL94Q8p4Dpkn@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linhaoguo86@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=sean@mess.org \
    --cc=stable@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.