public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Joe Perches <joe@perches.com>
Cc: "Mathieu Rhéaume" <mathieu@codingrhemes.com>,
	arve@android.com, dan.carpenter@oracle.com, mirsal@mirsal.fr,
	serban.constantinescu@arm.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: android: binder.c: Fixed 80 characters warnings from checkpatch.pl
Date: Tue, 1 Oct 2013 21:57:49 -0700	[thread overview]
Message-ID: <20131002045749.GA15121@kroah.com> (raw)
In-Reply-To: <1380678404.2081.21.camel@joe-AO722>

On Tue, Oct 01, 2013 at 06:46:44PM -0700, Joe Perches wrote:
> On Tue, 2013-10-01 at 21:39 -0400, Mathieu Rhéaume wrote:
> > Fixed a lot of warnings from checkpatch.pl about the 80 characters per line limitation.
> 
> I'd prefer
> 	s/binder_user_error/binder_user_err/
> or
> 	s/binder_user_error/binder_err/
> 
> without doing the strange wrapping
> 
> checkpatch will then exclude these long line formats from
> line length checking.
> 
> > diff --git a/drivers/staging/android/binder.c b/drivers/staging/android/binder.c
> []
> > @@ -663,7 +663,8 @@ static struct binder_buffer *binder_alloc_buf(struct binder_proc *proc,
> >  		ALIGN(offsets_size, sizeof(void *));
> >  
> >  	if (size < data_size || size < offsets_size) {
> > -		binder_user_error("%d: got transaction with invalid size %zd-%zd\n",
> > +		binder_user_error(
> > +		"%d: got transaction with invalid size %zd-%zd\n",
> >  				proc->pid, data_size, offsets_size);
> 
> IMO - not an improvement
> 

I agree, checkpatch is a guide, not a hard and fast rule.  For stuff
like this, it gets the line length wrong, so it's safe to leave it
alone.

greg k-h

  reply	other threads:[~2013-10-02  4:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02  1:39 [PATCH] Staging: android: binder.c: Fixed 80 characters warnings from checkpatch.pl Mathieu Rhéaume
2013-10-02  1:46 ` Joe Perches
2013-10-02  4:57   ` Greg KH [this message]
2013-10-02  7:51 ` Dan Carpenter

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=20131002045749.GA15121@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arve@android.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu@codingrhemes.com \
    --cc=mirsal@mirsal.fr \
    --cc=serban.constantinescu@arm.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