All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Frode Isaksen <fisaksen@baylibre.com>
Cc: linux-usb@vger.kernel.org, Thinh.Nguyen@synopsys.com,
	Frode Isaksen <frode@meta.com>
Subject: Re: [PATCH] usb: dwc3: gadget: check that event count does not exceed event buffer length
Date: Fri, 28 Mar 2025 11:07:03 +0100	[thread overview]
Message-ID: <2025032817-perceive-deeply-91ec@gregkh> (raw)
In-Reply-To: <CAJ03sU_Ad4nc=nvNU7Z+bjGYF35BEh_V5suWw+Vi0pb=imSpQA@mail.gmail.com>


A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Fri, Mar 28, 2025 at 10:57:46AM +0100, Frode Isaksen wrote:
> >What commit id does this fix?
> It fixes commit ebbb2d59398fb7ef92fae83d6aeba0cbb2b6f99f ("usb: dwc3:
> gadget: use evt->cache for processing events").

Great, please add a Fixes: tag.

> >Should it go to stable kernels too?
> Don't know, it happens extremely seldom. First seen on kernel 5.10.

So you do not think it should be applied to any older kernels?  If it is
a bugfix, it probably should.  Please resubmit with the proper cc:
stable tag as well.

thanks,

greg k-h

      reply	other threads:[~2025-03-28 10:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28  8:55 [PATCH] usb: dwc3: gadget: check that event count does not exceed event buffer length Frode Isaksen
2025-03-28  9:10 ` Greg KH
2025-03-28  9:57   ` Frode Isaksen
2025-03-28 10:07     ` Greg KH [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=2025032817-perceive-deeply-91ec@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=fisaksen@baylibre.com \
    --cc=frode@meta.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 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.