Linux USB
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: raoxu <raoxu@uniontech.com>
Cc: dengjie03@kylinos.cn, johannes.bruederl@gmail.com,
	kees@kernel.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, mathias.nyman@linux.intel.com,
	michal.pecio@gmail.com, sakari.ailus@linux.intel.com
Subject: Re: [RESEND PATCH] USB: core: report interrupt endpoint correctly in companion descriptor diagnostic
Date: Thu, 2 Jul 2026 13:55:38 +0200	[thread overview]
Message-ID: <2026070255-majestic-saddled-9bd5@gregkh> (raw)
In-Reply-To: <221217D28C1D901C+20260702092655.2567041-1-raoxu@uniontech.com>

On Thu, Jul 02, 2026 at 05:26:55PM +0800, raoxu wrote:
> Hi Greg,
> 
> > > interrupt endpoint because bulk endpoints are handled by the following
> > > else-if branch.
> > >
> > > Report the endpoint type as Interrupt instead of Bulk to avoid
> > > misleading descriptor diagnostics.
> > >
> > > Signed-off-by: Xu Rao <raoxu@uniontech.com>
> > > ---
> > >  drivers/usb/core/config.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Why is this RESEND?  Always say so below the --- line.
> 
> The original submission received an Acked-by, but it was not picked up.
> I resent the unchanged patch to bring it back to attention.

So you dropped the Ack now?  That's not ok, just respond to the original
thread.

But realize that the merge window just ended, and I'm staring down
thousands of pending patches.  If you wish to see patches applied
sooner, please help review other ones.

thanks,

rgeg k-h

      reply	other threads:[~2026-07-02 11:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02  8:11 [RESEND PATCH] usb: core: config: fix SS companion log for interrupt endpoints raoxu
2026-07-02  8:39 ` Greg KH
2026-07-02  9:25   ` [RESEND PATCH] USB: core: report interrupt endpoint correctly in companion descriptor diagnostic raoxu
2026-07-02  9:26   ` raoxu
2026-07-02 11:55     ` 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=2026070255-majestic-saddled-9bd5@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dengjie03@kylinos.cn \
    --cc=johannes.bruederl@gmail.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=michal.pecio@gmail.com \
    --cc=raoxu@uniontech.com \
    --cc=sakari.ailus@linux.intel.com \
    /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