public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Rex Nie <rex.nie@jaguarmicro.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Angus Chen <angus.chen@jaguarmicro.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: 答复: [PATCH v2] USB: core: remove dead code in do_proc_bulk()
Date: Sat, 9 Nov 2024 12:47:08 +0100	[thread overview]
Message-ID: <2024110911-professor-obnoxious-f411@gregkh> (raw)
In-Reply-To: <KL1PR0601MB5773F9F97A6AFC7E5D987323E65E2@KL1PR0601MB5773.apcprd06.prod.outlook.com>

On Sat, Nov 09, 2024 at 11:38:43AM +0000, Rex Nie wrote:
> 
> 
> > -----邮件原件-----
> > 发件人: Greg KH <gregkh@linuxfoundation.org>
> > 发送时间: 2024年11月9日 14:59
> > 收件人: Rex Nie <rex.nie@jaguarmicro.com>
> > 抄送: linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org; Angus Chen
> > <angus.chen@jaguarmicro.com>; stable@vger.kernel.org
> > 主题: Re: [PATCH v2] USB: core: remove dead code in do_proc_bulk()
> > 
> > External Mail: This email originated from OUTSIDE of the organization!
> > Do not click links, open attachments or provide ANY information unless you
> > recognize the sender and know the content is safe.
> > 
> > 
> > On Sat, Nov 09, 2024 at 10:11:41AM +0800, Rex Nie wrote:
> > > Since len1 is unsigned int, len1 < 0 always false. Remove it keep code
> > > simple.
> > >
> > > Cc: stable@vger.kernel.org
> > > Fixes: ae8709b296d8 ("USB: core: Make do_proc_control() and
> > > do_proc_bulk() killable")
> > > Signed-off-by: Rex Nie <rex.nie@jaguarmicro.com>
> > > ---
> > > changes in v2:
> > > - Add "Cc: stable@vger.kernel.org" (kernel test robot)
> > 
> > Why is this relevant for the stable kernels?  What bug is being fixed that
> > users would hit that this is needed to resolve?
> HI Greg k-h, I got a email from lkp@intel.com let me add Cc tag yesterday, so I apply v2 patch.

That was because you cc: stable and yet did not tag it as such.  That's
not passing a judgement call on if it should have been done at all,
which is what I am asking here.

> Although this shouldn't bother users, the expression len1 < 0 in the if condition doesn't make sense,
> and removing it makes the code more simple and efficient. The original email from kernel robot test
> shows as follows. I think it no need a cc tag either.

Does this follow the patches as per the documentation for what should be
accepted for stable kernels?

thanks,

greg k-h

  reply	other threads:[~2024-11-09 11:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-09  2:11 [PATCH v2] USB: core: remove dead code in do_proc_bulk() Rex Nie
2024-11-09  6:59 ` Greg KH
2024-11-09 11:38   ` 答复: " Rex Nie
2024-11-09 11:47     ` Greg KH [this message]
2024-11-11  8:01       ` 答复: " Rex Nie
2024-11-12 11:11         ` 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=2024110911-professor-obnoxious-f411@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=angus.chen@jaguarmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rex.nie@jaguarmicro.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