From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jerome Pouiller <Jerome.Pouiller@silabs.com>
Cc: Suraj Upadhyay <usuraj35@gmail.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@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:03:06 +0300 [thread overview]
Message-ID: <20200428190306.GM2014@kadam> (raw)
In-Reply-To: <8518467.FNpd3NTrYF@pc-42>
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.
Yeah. It's fine. It wasn't 100% cut and paste from my suggestions but
it did address the stuff I cared about. Thanks!
Reviewed-by: Dan Carpenter <dan.carpenter@oracle.com>
regards,
dan carpenter
prev parent reply other threads:[~2020-04-28 19:05 UTC|newest]
Thread overview: 5+ 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-27 11:50 ` Jerome Pouiller
2020-04-27 11:58 ` Suraj Upadhyay
2020-04-28 19:56 ` Dan Carpenter
2020-04-28 19:03 ` Dan Carpenter [this message]
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=20200428190306.GM2014@kadam \
--to=dan.carpenter@oracle.com \
--cc=Jerome.Pouiller@silabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox