All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Soumyajit Deb <debsoumyajit100@gmail.com>
Cc: outreachy-kernel@googlegroups.com, gregkh@linuxfoundation.org
Subject: Re: [Outreachy kernel] [Outreachy Kernel][PATCH 1/2] staging: wlang-ng: Properly align the lines of function call
Date: Mon, 30 Mar 2020 11:12:51 +0200	[thread overview]
Message-ID: <20200330111251.1d2e6db6@elisabeth> (raw)
In-Reply-To: <20200327144229.19738-2-debsoumyajit100@gmail.com>

On Fri, 27 Mar 2020 20:12:28 +0530
Soumyajit Deb <debsoumyajit100@gmail.com> wrote:

> Align the lines of function call to improve code readability and to
> adhere to the uniform Linux Kernel coding style.
> Reported by checkpatch.pl
> 
> Signed-off-by: Soumyajit Deb <debsoumyajit100@gmail.com>
> ---
>  drivers/staging/wlan-ng/cfg80211.c | 27 +++++++++++++--------------
>  1 file changed, 13 insertions(+), 14 deletions(-)
> 
> diff --git a/drivers/staging/wlan-ng/cfg80211.c b/drivers/staging/wlan-ng/cfg80211.c
> index fac38c842ac5..3d17037f954e 100644
> --- a/drivers/staging/wlan-ng/cfg80211.c
> +++ b/drivers/staging/wlan-ng/cfg80211.c
> @@ -359,16 +359,15 @@ static int prism2_scan(struct wiphy *wiphy,
>  		freq = ieee80211_channel_to_frequency(msg2.dschannel.data,
>  						      NL80211_BAND_2GHZ);
>  		bss = cfg80211_inform_bss(wiphy,
> -			ieee80211_get_channel(wiphy, freq),
> -			CFG80211_BSS_FTYPE_UNKNOWN,
> -			(const u8 *)&msg2.bssid.data.data,
> -			msg2.timestamp.data, msg2.capinfo.data,
> -			msg2.beaconperiod.data,
> -			ie_buf,
> -			ie_len,
> -			(msg2.signal.data - 65536) * 100, /* Conversion to signed type */
> -			GFP_KERNEL
> -		);
> +					  ieee80211_get_channel(wiphy, freq),
> +					  CFG80211_BSS_FTYPE_UNKNOWN,
> +					  (const u8 *)&msg2.bssid.data.data,
> +					  msg2.timestamp.data, msg2.capinfo.data,
> +					  msg2.beaconperiod.data,
> +					  ie_buf,
> +					  ie_len,
> +					  (msg2.signal.data - 65536) * 100, /* Conversion to signed type */

So... wait a moment:

- March 21, 17:30 UTC: you ask me on IRC how to fix the checkpatch
  warning you're introducing now. You propose to move the comment on a
  line by itself. I suggest that you write a test program and find out
  if this conversion can be done in another way. You say you will do
  that

- March 27, 10:58 UTC: you ask me on IRC if you can use a cast to "i32".
  I have a déjà vu, can't really remember who asked me this, and
  suggest that you write a test program. You say you will do that

- March 27, 12:12 UTC: you send the same question to this list

- March 27, 14:45 UTC: you send this patch

...why, exactly?

-- 
Stefano



  reply	other threads:[~2020-03-30  9:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 14:42 [Outreachy Kernel][PATCH 0/2] staging: wlan-ng: Resolve various warnings reported by checkpatch.pl Soumyajit Deb
2020-03-27 14:42 ` [Outreachy Kernel][PATCH 1/2] staging: wlang-ng: Properly align the lines of function call Soumyajit Deb
2020-03-30  9:12   ` Stefano Brivio [this message]
2020-03-30  9:55     ` [Outreachy kernel] " Soumyajit Deb
2020-03-30 10:14       ` Soumyajit Deb
2020-03-30 12:50         ` Stefano Brivio
2020-03-30 12:49       ` Stefano Brivio
2020-03-27 14:42 ` [Outreachy Kernel][PATCH 2/2] staging: wlan-ng: Line over 80 characters Soumyajit Deb

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=20200330111251.1d2e6db6@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=debsoumyajit100@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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.