From: josh@joshtriplett.org
To: Johannes Stadlinger <Johannes.Stadlinger@fau.de>
Cc: devel@linuxdriverproject.org,
Maximilian Eschenbacher <maximilian@eschenbacher.email>,
linux-kernel@i4.cs.fau.de,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Himangi Saraogi <himangi774@gmail.com>,
Vitaly Osipov <vitaly.osipov@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/8] wlan-ng/prism2mgmt:checkpatch: Insert blank line
Date: Thu, 19 Jun 2014 13:11:40 -0700 [thread overview]
Message-ID: <20140619201140.GB16404@cloud> (raw)
In-Reply-To: <1403205620-10219-3-git-send-email-Johannes.Stadlinger@fau.de>
On Thu, Jun 19, 2014 at 09:20:15PM +0200, Johannes Stadlinger wrote:
> This patch inserts a blank line after a declaration to avoid checkpatch
> warning.
>
> Signed-off-by: Johannes Stadlinger <Johannes.Stadlinger@fau.de>
> Signed-off-by: Maximilian Eschenbacher <maximilian@eschenbacher.email>
> CC: linux-kernel@i4.cs.fau.de
> CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> CC: Josh Triplett <josh@joshtriplett.org>
> CC: Himangi Saraogi <himangi774@gmail.com>
> CC: Vitaly Osipov <vitaly.osipov@gmail.com>
> CC: devel@driverdev.osuosl.org
> CC: linux-kernel@vger.kernel.org
This is one case where I think checkpatch is just wrong; this doesn't
make the code any more (or less) readable.
Meh-by: Josh Triplett <josh@joshtriplett.org>
> drivers/staging/wlan-ng/prism2mgmt.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/staging/wlan-ng/prism2mgmt.c b/drivers/staging/wlan-ng/prism2mgmt.c
> index f90f7da..e6a82d3 100644
> --- a/drivers/staging/wlan-ng/prism2mgmt.c
> +++ b/drivers/staging/wlan-ng/prism2mgmt.c
> @@ -190,6 +190,7 @@ int prism2mgmt_scan(wlandevice_t *wlandev, void *msgp)
> word = 0;
> for (i = 0; i < msg->channellist.data.len; i++) {
> u8 channel = msg->channellist.data.data[i];
> +
> if (channel > 14)
> continue;
> /* channel 1 is BIT 0 ... channel 14 is BIT 13 */
> --
> 1.9.1
>
next prev parent reply other threads:[~2014-06-19 20:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 19:20 [PATCH 1/8] wlan-ng/prism2mgmt:checkpatch: Fix long lines Johannes Stadlinger
2014-06-19 19:20 ` [PATCH 2/8] wlan-ng/prism2mgmt:checkpatch: Fix string split Johannes Stadlinger
2014-06-19 20:09 ` josh
2014-06-19 19:20 ` [PATCH 3/8] wlan-ng/prism2mgmt:checkpatch: Insert blank line Johannes Stadlinger
2014-06-19 20:11 ` josh [this message]
2014-06-20 8:14 ` Dan Carpenter
2014-06-19 19:20 ` [PATCH 4/8] wlan-ng/prism2mib:checkpatch: Fix string split Johannes Stadlinger
2014-06-19 20:12 ` josh
2014-06-19 19:20 ` [PATCH 5/8] wlan-ng/prism2mib:checkpatch: Insert blank lines Johannes Stadlinger
2014-06-19 20:14 ` josh
2014-06-19 20:25 ` Joe Perches
2014-06-19 19:20 ` [PATCH 6/8] wlan-ng/prism2sta:checkpatch: Fix long lines Johannes Stadlinger
2014-06-19 20:19 ` josh
2014-06-19 20:22 ` Joe Perches
2014-06-19 19:20 ` [PATCH 7/8] wlan-ng/prism2sta:checkpatch: Fix string split Johannes Stadlinger
2014-06-19 20:20 ` josh
2014-06-19 19:20 ` [PATCH 8/8] wlan-ng/prism2sta:checkpatch: Insert blank lines Johannes Stadlinger
2014-06-19 20:20 ` josh
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=20140619201140.GB16404@cloud \
--to=josh@joshtriplett.org \
--cc=Johannes.Stadlinger@fau.de \
--cc=devel@driverdev.osuosl.org \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=himangi774@gmail.com \
--cc=linux-kernel@i4.cs.fau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maximilian@eschenbacher.email \
--cc=vitaly.osipov@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 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.