mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Oliver N. Baumann" <oliver.n.baumann@googlemail.com>
Cc: sjakub@gmail.com, pq@iki.fi, baumanno@cip.ifi.lmu.de,
	kernel@kenobrien.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: asus_oled: fix checkpatch.pl issue in asus_oled.c
Date: Tue, 28 Feb 2012 19:46:32 -0800	[thread overview]
Message-ID: <20120229034632.GA22450@kroah.com> (raw)
In-Reply-To: <1330486491-8699-1-git-send-email-baumanno@cip.ifi.lmu.de>

On Wed, Feb 29, 2012 at 04:34:51AM +0100, Oliver N. Baumann wrote:
> From: "Oliver N. Baumann" <baumanno@cip.ifi.lmu.de>
> 
> This is a patch to asus_oled.c that fixes a parenthesis issue detected by checkpatch.pl tool
> Signed-off-by: Oliver N. Baumann <baumanno@cip.ifi.lmu.de>

You need a blank line between the changelog text and the signed-off-by
line.

Also, please wrap your changelog entry at 72 columns.

But most of all:

> ---
>  drivers/staging/asus_oled/asus_oled.c |    6 +++---
>  1 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/asus_oled/asus_oled.c b/drivers/staging/asus_oled/asus_oled.c
> index 1df9586..b77f225 100644
> --- a/drivers/staging/asus_oled/asus_oled.c
> +++ b/drivers/staging/asus_oled/asus_oled.c
> @@ -44,9 +44,9 @@
>  
>  #define ASUS_OLED_ERROR			"Asus OLED Display Error: "
>  
> -#define ASUS_OLED_STATIC		's'
> -#define ASUS_OLED_ROLL			'r'
> -#define ASUS_OLED_FLASH			'f'
> +#define ASUS_OLED_STATIC		('s')
> +#define ASUS_OLED_ROLL			('r')
> +#define ASUS_OLED_FLASH			('f')

That's not a valid change, checkpatch is being stupid here, please use
your judgement.  This patch changes nothing, go bug the checkpatch
people to fix their tool.

greg k-h

      reply	other threads:[~2012-02-29  3:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29  3:34 Oliver N. Baumann
2012-02-29  3:46 ` 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=20120229034632.GA22450@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=baumanno@cip.ifi.lmu.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=kernel@kenobrien.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver.n.baumann@googlemail.com \
    --cc=pq@iki.fi \
    --cc=sjakub@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

all inboxes | Powered by JetHome®