Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Peter Chen <peter.chen@cixtech.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: fugang.duan@cixtech.com, cix-kernel-upstream@cixtech.com,
	stable@vger.kernel.org,
	Hongliang Yang <hongliang.yang@cixtech.com>
Subject: Re: [PATCH 1/1] usb: cdnsp: do not disable slot for disabled slot
Date: Tue, 1 Jul 2025 17:43:05 +0800	[thread overview]
Message-ID: <aGOtqYXkxxcnHAl-@nchen-desktop> (raw)
In-Reply-To: <2025070123-macaroni-gag-6dd0@gregkh>

On 25-07-01 11:34:46, Greg KH wrote:
> [Some people who received this message don't often get email from gregkh@linuxfoundation.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> 
> EXTERNAL EMAIL
> 
> On Wed, Jun 18, 2025 at 05:53:21PM +0800, Peter Chen wrote:
> > It doesn't need to do it, and the related command event returns
> > 'Slot Not Enabled Error' status.
> >
> > Fixes: 3d82904559f4 ("usb: cdnsp: cdns3 Add main part of Cadence USBSSP DRD Driver")
> > cc: stable@vger.kernel.org
> > Suggested-by: Hongliang Yang <hongliang.yang@cixtech.com>
> > Signed-off-by: Peter Chen <peter.chen@cixtech.com>
> > ---
> >  drivers/usb/cdns3/cdnsp-ring.c | 4 +++-
> >  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> Any reason this wasn't cc:ed the proper mailing lists?
> 
> Or is this a stable-kernel-only patch?
> 
> confused,

Sorry, Greg. This is internal review patch for upstream, I forgot to
omit cc list when sending review. Please ignore it.

The formal upstream patch has already sent out to linux-usb mail list.

-- 

Best regards,
Peter

  reply	other threads:[~2025-07-01  9:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18  9:53 [PATCH 1/1] usb: cdnsp: do not disable slot for disabled slot Peter Chen
2025-06-18 13:04 ` 回复: " Fugang Duan
2025-07-01  9:34 ` Greg KH
2025-07-01  9:43   ` Peter Chen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-19  1:34 Peter Chen

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=aGOtqYXkxxcnHAl-@nchen-desktop \
    --to=peter.chen@cixtech.com \
    --cc=cix-kernel-upstream@cixtech.com \
    --cc=fugang.duan@cixtech.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hongliang.yang@cixtech.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