From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Philip Potter <phil@philpotter.co.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Pavel Skripkin <paskripkin@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
David Laight <david.Laight@aculab.com>
Subject: Re: [PATCH v5 15/19] staging: r8188eu: hal: Clean up usbctrl_vendorreq()
Date: Wed, 15 Sep 2021 16:59:03 +0200 [thread overview]
Message-ID: <3504293.VdliR8Xgxp@localhost.localdomain> (raw)
In-Reply-To: <20210915135301.GF2088@kadam>
On Wednesday, September 15, 2021 3:53:01 PM CEST Dan Carpenter wrote:
> On Wed, Sep 15, 2021 at 02:41:45PM +0200, Fabio M. De Francesco wrote:
> > Clean up usbctrl_vendoreq () in usb_ops_linux.c. Eventually this function
> > will be deleted but some of the code will be reused later. This cleanup
> > makes code reuse easier.
> >
> Thanks for removing the URL. This commit message is no longer bad to
> the point where it has to be redone but it's still not great.
>
> I explicitly told you to leave the irrelevant information out. I'm
> trying to help you and it's frustrating that you're not listening. I
> wish that you had just copy and pasted the commit message which I sent.
I'm sorry, seriously. It's hard to listen carefully when I need to do my
*real* work while trying my best to contribute to the kernel. Sometimes I'm
so tired that I forget something important or what it is said by reviewers. I
know that this is not a good excuse, anyway please don't ever think that I
don't mind of the time you spend on reviews and writing suggestions.
> This relates the discussion we had about reviewing patches one at a time
> in the order they arrive. Every patch should be self contained. It
> should not refer to the past except in the case of explaining the Fixes
> tag and it should not refer to the future except in the case where it
> needs to excuse adding unused infrastructure. Reviewing is stateless.
> We don't want to know about your plans.
>
> On the other hand, the commit message doesn't list the changes the
> commit makes as part of the clean up process. That would have been
> helpful information for me as a reviewer.
>
> *Sigh* Whatever... I would have allowed this commit message but there
> is a bug in the code.
>
> > + memcpy(data, io_buf, len);
> > + } else {
> > + /* errors */
> > if (status < 0) {
> > - if (status == (-ESHUTDOWN) ||
status == -ENODEV) {
> > + if (status == (-ESHUTDOWN || -
ENODEV)) {
>
> This is a bug so you'll have to redo the patch.
This is the proof of what I was trying to convey with the words above. I
perfectly knew, since days, that this line is wrong but for some reason that
I really cannot understand why it's still there.
Thank you very much,
Fabio
> regards,
> dan carpenter
>
next prev parent reply other threads:[~2021-09-15 14:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 12:41 [PATCH v5 00/19] staging: r8188eu: Shorten and simplify calls chain Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 01/19] staging: r8188eu: remove usb_{read,write}_mem Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 02/19] staging: r8188eu: remove the helpers of rtw_read8() Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 03/19] staging: r8188eu: remove the helpers of rtw_read16() Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 04/19] staging: r8188eu: remove the helpers of rtw_read32() Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 05/19] staging: r8188eu: remove the helpers of usb_write8 Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 06/19] staging: r8188eu: remove the helpers of usb_write16 Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 07/19] staging: r8188eu: remove the helpers of usb_write32 Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 08/19] staging: r8188eu: remove the helpers of usb_writeN() Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 09/19] staging: r8188eu: remove the helpers of usb_read_port() Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 10/19] staging: r8188eu: remove the helpers of usb_write_port() Fabio M. De Francesco
2021-09-15 16:06 ` Larry Finger
2021-09-15 17:40 ` Pavel Skripkin
2021-09-15 12:41 ` [PATCH v5 11/19] staging: r8188eu: remove the helpers of usb_read_port_cancel() Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 12/19] staging: r8188eu: remove the helpers of usb_write_port_cancel() Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 13/19] staging: r8188eu: remove core/rtw_io.c Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 14/19] staging: remove struct _io_ops Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 15/19] staging: r8188eu: hal: Clean up usbctrl_vendorreq() Fabio M. De Francesco
2021-09-15 13:53 ` Dan Carpenter
2021-09-15 14:59 ` Fabio M. De Francesco [this message]
2021-09-15 12:41 ` [PATCH v5 16/19] staging: r8188eu: hal: Clean up rtw_read*() and rtw_write*() Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 17/19] staging: r8188eu: Shorten calls chain of rtw_read8/16/32() Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 18/19] staging: r8188eu: Shorten calls chain of rtw_write8/16/32/N() Fabio M. De Francesco
2021-09-15 12:41 ` [PATCH v5 19/19] staging: r8188eu: remove shared buffer for usb requests Fabio M. De Francesco
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=3504293.VdliR8Xgxp@localhost.localdomain \
--to=fmdefrancesco@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=david.Laight@aculab.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=paskripkin@gmail.com \
--cc=phil@philpotter.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).