From: Abhishek Tamboli <abhishektamboli9@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: gregkh@linuxfoundation.org, usb-storage@lists.one-eyed-alien.net,
linux-usb@vger.kernel.org, skhan@linuxfoundation.org,
dan.carpenter@linaro.org, rbmarliere@gmail.com,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: storage: ene_ub6250: Fix right shift warnings
Date: Thu, 12 Sep 2024 06:15:18 +0530 [thread overview]
Message-ID: <ZuI5nptdk+BcXh+R@embed-PC.myguest.virtualbox.org> (raw)
In-Reply-To: <890e0ed1-25c3-414e-9e8e-f5925fe8c778@rowland.harvard.edu>
Hi Alan,
On Thu, Aug 01, 2024 at 10:51:35AM -0400, Alan Stern wrote:
> On Thu, Aug 01, 2024 at 08:54:18AM +0200, 'Oliver Neukum' via USB Mass Storage on Linux wrote:
> >
> >
> > On 31.07.24 20:19, Alan Stern wrote:
> > > On Wed, Jul 31, 2024 at 11:34:45PM +0530, Abhishek Tamboli wrote:
> > > > On Wed, Jul 31, 2024 at 10:04:33AM -0400, Alan Stern wrote:
> >
> > Hi,
> >
> > I should make my reasoning clearer.
> >
> > > > > Replacing the variable with a constant won't make much difference. The
> > > > > compiler will realize that bl_len has a constant value and will generate
> > > > > appropriate code anyway. I think just changing the type is a fine fix.
> >
> > While that is absolutely true, it kind of removes the reason for the patch
> > in the first place. The code gcc generates is unlikely to be changed.
> >
> > We are reacting to a warning an automatic tool generates. That is a good thing.
> > We should have clean code. The question is how we react to such a report.
> > It just seems to me that if we fix such a warning, the code should really be clean
> > after that. Just doing the minimum that will make the checker shut up is
> > no good.
>
> With this fix, the code seems clean to me. It may not be as short as
> possible, but it's clean.
I noticed that the patch has not yet been pulled into linux-next,
even though it has been acked-by you for over a month. Is there
anything else I need to do on my end?
Thank you for your attention to this matter.
Regards,
Abhishek
next prev parent reply other threads:[~2024-09-12 0:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 18:23 [PATCH] usb: storage: ene_ub6250: Fix right shift warnings Abhishek Tamboli
2024-07-29 18:34 ` Alan Stern
2024-07-30 7:09 ` Oliver Neukum
2024-07-30 17:56 ` Abhishek Tamboli
2024-07-31 9:15 ` Oliver Neukum
2024-07-31 14:04 ` Alan Stern
2024-07-31 18:04 ` Abhishek Tamboli
2024-07-31 18:19 ` Alan Stern
2024-07-31 19:18 ` Abhishek Tamboli
2024-08-01 6:54 ` Oliver Neukum
2024-08-01 14:51 ` Alan Stern
2024-09-12 0:45 ` Abhishek Tamboli [this message]
2024-09-12 1:24 ` Alan Stern
2024-09-12 5:06 ` Greg KH
2024-09-12 14:50 ` Abhishek Tamboli
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=ZuI5nptdk+BcXh+R@embed-PC.myguest.virtualbox.org \
--to=abhishektamboli9@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rbmarliere@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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