From: Greg KH <gregkh@linuxfoundation.org>
To: Merwin Trever Ferrao <merwintf@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 16/16] Staging: wlan-ng: cfg80211: fixed alignment issue with open parenthesis line ending with (
Date: Mon, 10 Jun 2019 17:48:02 +0200 [thread overview]
Message-ID: <20190610154802.GA29035@kroah.com> (raw)
In-Reply-To: <20190610103825.19364-1-merwintf@gmail.com>
On Mon, Jun 10, 2019 at 04:08:25PM +0530, Merwin Trever Ferrao wrote:
> From: Merwin Trever Ferrao <Merwintf@gmail.com>
>
> Fixed a coding style issue.
>
> Signed-off-by: Merwin Trever Ferrao <merwintf@gmail.com>
> ---
> drivers/staging/wlan-ng/cfg80211.c | 32 ++++++++++++++----------------
> 1 file changed, 15 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/staging/wlan-ng/cfg80211.c b/drivers/staging/wlan-ng/cfg80211.c
> index eee1998c4b18..5424e2682911 100644
> --- a/drivers/staging/wlan-ng/cfg80211.c
> +++ b/drivers/staging/wlan-ng/cfg80211.c
> @@ -324,8 +324,7 @@ static int prism2_scan(struct wiphy *wiphy,
> (i < request->n_channels) && i < ARRAY_SIZE(prism2_channels);
> i++)
> msg1.channellist.data.data[i] =
> - ieee80211_frequency_to_channel(
> - request->channels[i]->center_freq);
> + ieee80211_frequency_to_channel(request->channels[i]->center_freq);
And now you violate the other coding style rule of too long lines :(
You can just keep sending patches fixing this back and forth, if you
want a never-ending set of patches to be applied, but we don't really
like that.
So the code is ok as-is.
> msg1.channellist.data.len = request->n_channels;
>
> msg1.maxchanneltime.data = 250;
> @@ -359,15 +358,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 */
> + GFP_KERNEL
> );
Why is this final ); way over here?
>
> if (!bss) {
> @@ -475,14 +474,13 @@ static int prism2_connect(struct wiphy *wiphy, struct net_device *dev,
> }
>
> result = prism2_domibset_uint32(wlandev,
> - DIDMIB_DOT11SMT_PRIVACYTABLE_WEPDEFAULTKEYID,
> - sme->key_idx);
> + DIDMIB_DOT11SMT_PRIVACYTABLE_WEPDEFAULTKEYID,
> + sme->key_idx);
> if (result)
> goto exit;
>
> /* send key to driver */
> - did = didmib_dot11smt_wepdefaultkeystable_key(
> - sme->key_idx + 1);
> + did = didmib_dot11smt_wepdefaultkeystable_key(sme->key_idx + 1);
Too long of a line.
Remember, checkpatch is just a "hint", you still have to use your brain
when looking at the output of it.
thanks,
greg k-h
prev parent reply other threads:[~2019-06-10 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 10:38 [PATCH 16/16] Staging: wlan-ng: cfg80211: fixed alignment issue with open parenthesis line ending with ( Merwin Trever Ferrao
2019-06-10 15:48 ` 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=20190610154802.GA29035@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=merwintf@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