All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Roy Luo <royluo@google.com>
Cc: stern@rowland.harvard.edu, badhri@google.com,
	quic_kriskura@quicinc.com, francesco.dolcini@toradex.com,
	quic_eserrao@quicinc.com, ivan.orlov0322@gmail.com,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] USB: gadget: core: adjust uevent timing on gadget unbind
Date: Tue, 28 Nov 2023 19:01:08 +0000	[thread overview]
Message-ID: <2023112835-sediment-subsidy-7e99@gregkh> (raw)
In-Reply-To: <CA+zupgxfxaB_bO51ZXW+5T3-FMF94=Tm+mqZ92LCYBZtwiQd3A@mail.gmail.com>

On Tue, Nov 28, 2023 at 10:52:49AM -0800, Roy Luo wrote:
> On Tue, Nov 28, 2023 at 12:00 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> > - You have marked a patch with a "Fixes:" tag for a commit that is in an
> >   older released kernel, yet you do not have a cc: stable line in the
> >   signed-off-by area at all, which means that the patch will not be
> >   applied to any older kernel releases.  To properly fix this, please
> >   follow the documented rules in the
> >   Documentation/process/stable-kernel-rules.rst file for how to resolve
> >   this.
> 
> I don't see a need for this patch to go into stable kernels after
> reviewing Documentation/process/stable-kernel-rules.rst, please let me
> know if you think otherwise.

If you think this fixes a bug in the existing code, why wouldn't it be
needed?

Also, this implies that you will not be wanting it backported to any
chromeos or android kernels?

thanks,

greg k-h

  reply	other threads:[~2023-11-28 19:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 22:00 [PATCH v2] USB: gadget: core: adjust uevent timing on gadget unbind Roy Luo
2023-11-28  8:00 ` Greg KH
2023-11-28 18:52   ` Roy Luo
2023-11-28 19:01     ` Greg KH [this message]
2023-11-28 22:14       ` Roy Luo

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=2023112835-sediment-subsidy-7e99@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=badhri@google.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=ivan.orlov0322@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=quic_eserrao@quicinc.com \
    --cc=quic_kriskura@quicinc.com \
    --cc=royluo@google.com \
    --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.