public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Tugce Sirin <ztugcesirin@gmail.com>,
	Neil Armstrong <superna9999@gmail.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Vitaly Osipov <vitaly.osipov@gmail.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/8] wlan-ng/prism2sta:checkpatch: Fix long lines
Date: Thu, 19 Jun 2014 13:19:54 -0700	[thread overview]
Message-ID: <20140619201954.GF16404@cloud> (raw)
In-Reply-To: <1403205620-10219-6-git-send-email-Johannes.Stadlinger@fau.de>

On Thu, Jun 19, 2014 at 09:20:18PM +0200, Johannes Stadlinger wrote:
> This patch fixes all warning of checkpatch about lines over 80
> characters.
> 
> 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: Tugce Sirin <ztugcesirin@gmail.com>
> CC: Josh Triplett <josh@joshtriplett.org>
> CC: Neil Armstrong <superna9999@gmail.com>
> CC: Paul Gortmaker <paul.gortmaker@windriver.com>
> CC: Vitaly Osipov <vitaly.osipov@gmail.com>
> CC: devel@driverdev.osuosl.org
> CC: linux-kernel@vger.kernel.org

Most of these look fine, but...

> @@ -1271,7 +1275,8 @@ void prism2sta_processing_defer(struct work_struct *data)
>  				     HFA384x_RID_CURRENTSSID, result);
>  				return;
>  			}
> -			prism2mgmt_bytestr2pstr((struct hfa384x_bytestr *) &ssid,
> +			prism2mgmt_bytestr2pstr((struct hfa384x_bytestr *)
> +									&ssid,
>  						(p80211pstrd_t *) &
>  						wlandev->ssid);

...that (and the one in the subsequent context lines) looks horrible.
I'd suggest breaking after the opening parenthesis of the function call
and just indenting the arguments by one tab:
	foo_with_long_name(
		long_arg,
		another_long_arg);

Better yet, ignore checkpatch and format that call more readably as
though the 80 column rule didn't exist.

  reply	other threads:[~2014-06-19 20:20 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
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 [this message]
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=20140619201954.GF16404@cloud \
    --to=josh@joshtriplett.org \
    --cc=Johannes.Stadlinger@fau.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@i4.cs.fau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maximilian@eschenbacher.email \
    --cc=paul.gortmaker@windriver.com \
    --cc=superna9999@gmail.com \
    --cc=vitaly.osipov@gmail.com \
    --cc=ztugcesirin@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