All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Madhumitha Prabakaran <madhumithabiw@gmail.com>
Cc: forest@alittletooquiet.net, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v3] Staging: vt6655: Alignment of function parameters
Date: Wed, 27 Feb 2019 15:47:44 +0100	[thread overview]
Message-ID: <20190227144744.GD21288@kroah.com> (raw)
In-Reply-To: <20190226200150.2708-1-madhumithabiw@gmail.com>

On Tue, Feb 26, 2019 at 02:01:50PM -0600, Madhumitha Prabakaran wrote:
> This patch align the function parameters to improve readibility.
> 
> Signed-off-by: Madhumitha Prabakaran <madhumithabiw@gmail.com>
> 
> ---
> Changes in v2
> -Make a commit message imperative
> -Use multiple lines to improve readibility
> 
> Changes in v3
> -Commit message and subject line are modified
> -Alignment of function parameters
> ---
>  drivers/staging/vt6655/baseband.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/vt6655/baseband.c b/drivers/staging/vt6655/baseband.c
> index 35bbff807df9..e3fecd732c88 100644
> --- a/drivers/staging/vt6655/baseband.c
> +++ b/drivers/staging/vt6655/baseband.c
> @@ -1705,9 +1705,9 @@ static const unsigned short awcFrameTime[MAX_RATE] = {
>   *
>   */
>  unsigned int BBuGetFrameTime(unsigned char byPreambleType,
> -	unsigned char byPktType,
> -	unsigned int cbFrameLength,
> -	unsigned short wRate)
> +		unsigned char byPktType,
> +		unsigned int cbFrameLength,
> +		unsigned short wRate)

They should line up with the variable above it, so this should end up
looking like:
unsigned int BBuGetFrameTime(unsigned char byPreambleType,
			     unsigned char byPktType,
			     unsigned int cbFrameLength,
			     unsigned short wRate)

But, given that there is no need to put one variable per line, you can
shorten this and make it look like:

unsigned int BBuGetFrameTime(unsigned char byPreambleType,
			     unsigned char byPktType,
			     unsigned int cbFrameLength, unsigned short wRate)

thanks,

greg k-h


      reply	other threads:[~2019-02-27 14:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26 20:01 [PATCH v3] Staging: vt6655: Alignment of function parameters Madhumitha Prabakaran
2019-02-27 14:47 ` Greg KH [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=20190227144744.GD21288@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.