From: Dan Carpenter <dan.carpenter@oracle.com>
To: Suraj Upadhyay <usuraj35@gmail.com>
Cc: devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] staging: wfx: cleanup long lines in data_tx.c
Date: Tue, 28 Apr 2020 19:56:00 +0000 [thread overview]
Message-ID: <20200428195600.GN2014@kadam> (raw)
In-Reply-To: <20200427115827.GA3214@blackclown>
On Mon, Apr 27, 2020 at 05:28:27PM +0530, Suraj Upadhyay wrote:
> On Mon, Apr 27, 2020 at 11:50:23AM +0000, Jerome Pouiller wrote:
> > On Saturday 25 April 2020 13:32:34 CEST Suraj Upadhyay wrote:
> > > Break lines with length over 80 characters to
> > > conform to the linux coding style and refactor
> > > wherever necessary.
> > >
> > > Signed-off-by: Suraj Upadhyay <usuraj35@gmail.com>
> > > ---
> > >
> > > Changes in v4:
> > > - Added a space after declaration in wfx_get_hw_rate().
> > > - A checkpatch warning for this commit is retained at line 75,
> > > to maintain uniformity in function declarations. (Reviewer
> > > jerome suggested).
> > >
> > > Changes in v3:
> > > - Changed the temporary variable name for the memzcmp statement
> > > to is_used. (as suggested).
> > > - Added a temporary ieee80211_supported_band variable to address
> > > the problem in wfx_get_hw_rate() more efficiently. (not
> > > suggested, but still).
> > >
> > > Changes in v2:
> > > - Introduced a temporary variable for the memzcmp statement.
> > > - Addressed the checkpatch problem with wfx_get_hw_rate().
> > > - Restored the function definition of wfx_tx_get_tx_parms
> > > as suggested by the reviewer.
> > > - Added suggested changes for req->packet_id statement.
> > >
> > > drivers/staging/wfx/data_tx.c | 40 +++++++++++++++++++++++------------
> > > 1 file changed, 26 insertions(+), 14 deletions(-)
> >
> > This patch does not contain the suggestions from Dan. However, it is
> > sufficient from my personal point of view.
>
> Yes, I considered them but thought it would be bad to introduce a new
> variable at every iteration of the for-loop.
>
It's not bad at all. I don't know why someone would think that.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Suraj Upadhyay <usuraj35@gmail.com>
Cc: Jerome Pouiller <Jerome.Pouiller@silabs.com>,
devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] staging: wfx: cleanup long lines in data_tx.c
Date: Tue, 28 Apr 2020 22:56:00 +0300 [thread overview]
Message-ID: <20200428195600.GN2014@kadam> (raw)
In-Reply-To: <20200427115827.GA3214@blackclown>
On Mon, Apr 27, 2020 at 05:28:27PM +0530, Suraj Upadhyay wrote:
> On Mon, Apr 27, 2020 at 11:50:23AM +0000, Jerome Pouiller wrote:
> > On Saturday 25 April 2020 13:32:34 CEST Suraj Upadhyay wrote:
> > > Break lines with length over 80 characters to
> > > conform to the linux coding style and refactor
> > > wherever necessary.
> > >
> > > Signed-off-by: Suraj Upadhyay <usuraj35@gmail.com>
> > > ---
> > >
> > > Changes in v4:
> > > - Added a space after declaration in wfx_get_hw_rate().
> > > - A checkpatch warning for this commit is retained at line 75,
> > > to maintain uniformity in function declarations. (Reviewer
> > > jerome suggested).
> > >
> > > Changes in v3:
> > > - Changed the temporary variable name for the memzcmp statement
> > > to is_used. (as suggested).
> > > - Added a temporary ieee80211_supported_band variable to address
> > > the problem in wfx_get_hw_rate() more efficiently. (not
> > > suggested, but still).
> > >
> > > Changes in v2:
> > > - Introduced a temporary variable for the memzcmp statement.
> > > - Addressed the checkpatch problem with wfx_get_hw_rate().
> > > - Restored the function definition of wfx_tx_get_tx_parms
> > > as suggested by the reviewer.
> > > - Added suggested changes for req->packet_id statement.
> > >
> > > drivers/staging/wfx/data_tx.c | 40 +++++++++++++++++++++++------------
> > > 1 file changed, 26 insertions(+), 14 deletions(-)
> >
> > This patch does not contain the suggestions from Dan. However, it is
> > sufficient from my personal point of view.
>
> Yes, I considered them but thought it would be bad to introduce a new
> variable at every iteration of the for-loop.
>
It's not bad at all. I don't know why someone would think that.
regards,
dan carpenter
next prev parent reply other threads:[~2020-04-28 19:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 11:32 [PATCH v4] staging: wfx: cleanup long lines in data_tx.c Suraj Upadhyay
2020-04-25 11:44 ` Suraj Upadhyay
2020-04-27 11:50 ` Jerome Pouiller
2020-04-27 11:50 ` Jerome Pouiller
2020-04-27 11:58 ` Suraj Upadhyay
2020-04-27 11:58 ` Suraj Upadhyay
2020-04-28 19:56 ` Dan Carpenter [this message]
2020-04-28 19:56 ` Dan Carpenter
2020-04-28 19:03 ` Dan Carpenter
2020-04-28 19:03 ` Dan Carpenter
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=20200428195600.GN2014@kadam \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=usuraj35@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.