From: Greg KH <gregkh@linuxfoundation.org>
To: Madhumitha Prabakaran <madhumithabiw@gmail.com>
Cc: forest@alittletooquiet.net, outreachy-kernel@googlegroups.com
Subject: Re: [PATCH] Staging: vt6655: Fix check - Lines should not end with a '('
Date: Tue, 26 Feb 2019 11:44:29 +0100 [thread overview]
Message-ID: <20190226104429.GA20834@kroah.com> (raw)
In-Reply-To: <20190225180235.14346-1-madhumithabiw@gmail.com>
On Mon, Feb 25, 2019 at 12:02:35PM -0600, Madhumitha Prabakaran wrote:
> Improve readibility
>
> Signed-off-by: Madhumitha Prabakaran <madhumithabiw@gmail.com>
> ---
> drivers/staging/vt6655/card.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/staging/vt6655/card.c b/drivers/staging/vt6655/card.c
> index 5dedc7aad384..6042f0bcd3f8 100644
> --- a/drivers/staging/vt6655/card.c
> +++ b/drivers/staging/vt6655/card.c
> @@ -62,12 +62,11 @@ static const unsigned short cwRXBCNTSFOff[MAX_RATE] = {
>
> static
> void
> -s_vCalculateOFDMRParameter(
> - unsigned char byRate,
> - u8 bb_type,
> - unsigned char *pbyTxRate,
> - unsigned char *pbyRsvTime
> -);
> +s_vCalculateOFDMRParameter
> + (unsigned char byRate,
> + u8 bb_type,
> + unsigned char *pbyTxRate,
> + unsigned char *pbyRsvTime);
There's so much wrong with these few lines to start with, you can make
this look a lot better all at once.
How about this change instead:
static void s_vCalculateOFDMRParameter(unsigned char byRate, u8 bb_type,
unsigned char *pbyTxRate,
unsigned char *pbyRsvTime);
Isn't that much more readable over the initial, and even your change?
thanks,
greg k-h
next prev parent reply other threads:[~2019-02-26 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 18:02 [PATCH] Staging: vt6655: Fix check - Lines should not end with a '(' Madhumitha Prabakaran
2019-02-26 10:44 ` Greg KH [this message]
2019-02-26 12:40 ` Madhumthia Prabakaran
-- strict thread matches above, loose matches on Subject: below --
2019-02-25 18:13 Madhumitha Prabakaran
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=20190226104429.GA20834@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=forest@alittletooquiet.net \
--cc=madhumithabiw@gmail.com \
--cc=outreachy-kernel@googlegroups.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.