From: 'Maxime Ripard' <maxime.ripard@free-electrons.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] video: hx8357: Make IM pins optional
Date: Fri, 19 Jul 2013 08:35:55 +0000 [thread overview]
Message-ID: <20130719083555.GC5106@lukather> (raw)
In-Reply-To: <1373945380.7549.26.camel@marge.simpson.net>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
Hi Jingoo, Mike,
On Tue, Jul 16, 2013 at 05:29:40AM +0200, Mike Galbraith wrote:
> On Tue, 2013-07-16 at 09:49 +0900, Jingoo Han wrote:
> > On Tuesday, July 16, 2013 12:27 AM, Maxime Ripard wrote:
>
> > > +
> > > + ret = devm_gpio_request_one(&spi->dev, lcd->im_pins[i],
> > > + GPIOF_OUT_INIT_LOW, "im_pins");
> >
> > This makes a checkpatch warning such as 'WARNING: line over 80 characters'.
> > How about the following?
> >
> > ret = devm_gpio_request_one(&spi->dev, lcd->im_pins[i],
> > GPIOF_OUT_INIT_LOW, "im_pins");
>
> IIRC, some maintainers gripe (davem?) when they see such alignment,
> preferring the original arg below arg alignment vs strict 80 column.
As far as I know, the coding guide styles are quite fuzzy about this:
- The new line is not required to be aligned with the braces above
- Yet, the emacs config given does indent like this.
- 80 characters is said not to be a hard limit
I don't really know if there's a better solution here, except maybe:
ret = devm_gpio_request_one(&spi-dev, lcd->im_pins[i],
GPIOF_OUT_INIT_LOW,
"im_pins");
But it's not really a big deal, is it?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: maxime.ripard@free-electrons.com ('Maxime Ripard')
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] video: hx8357: Make IM pins optional
Date: Fri, 19 Jul 2013 10:35:55 +0200 [thread overview]
Message-ID: <20130719083555.GC5106@lukather> (raw)
In-Reply-To: <1373945380.7549.26.camel@marge.simpson.net>
Hi Jingoo, Mike,
On Tue, Jul 16, 2013 at 05:29:40AM +0200, Mike Galbraith wrote:
> On Tue, 2013-07-16 at 09:49 +0900, Jingoo Han wrote:
> > On Tuesday, July 16, 2013 12:27 AM, Maxime Ripard wrote:
>
> > > +
> > > + ret = devm_gpio_request_one(&spi->dev, lcd->im_pins[i],
> > > + GPIOF_OUT_INIT_LOW, "im_pins");
> >
> > This makes a checkpatch warning such as 'WARNING: line over 80 characters'.
> > How about the following?
> >
> > ret = devm_gpio_request_one(&spi->dev, lcd->im_pins[i],
> > GPIOF_OUT_INIT_LOW, "im_pins");
>
> IIRC, some maintainers gripe (davem?) when they see such alignment,
> preferring the original arg below arg alignment vs strict 80 column.
As far as I know, the coding guide styles are quite fuzzy about this:
- The new line is not required to be aligned with the braces above
- Yet, the emacs config given does indent like this.
- 80 characters is said not to be a hard limit
I don't really know if there's a better solution here, except maybe:
ret = devm_gpio_request_one(&spi-dev, lcd->im_pins[i],
GPIOF_OUT_INIT_LOW,
"im_pins");
But it's not really a big deal, is it?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130719/bc2fea0e/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: "'Maxime Ripard'" <maxime.ripard@free-electrons.com>
To: Mike Galbraith <bitbucket@online.de>
Cc: Jingoo Han <jg1.han@samsung.com>,
"'Andrew Morton'" <akpm@linux-foundation.org>,
"'Alexandre Belloni'" <alexandre.belloni@free-electrons.com>,
hector.palacios@digi.com,
"'Thomas Petazzoni'" <thomas@free-electrons.com>,
plagnioj@jcrosoft.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 2/3] video: hx8357: Make IM pins optional
Date: Fri, 19 Jul 2013 10:35:55 +0200 [thread overview]
Message-ID: <20130719083555.GC5106@lukather> (raw)
In-Reply-To: <1373945380.7549.26.camel@marge.simpson.net>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
Hi Jingoo, Mike,
On Tue, Jul 16, 2013 at 05:29:40AM +0200, Mike Galbraith wrote:
> On Tue, 2013-07-16 at 09:49 +0900, Jingoo Han wrote:
> > On Tuesday, July 16, 2013 12:27 AM, Maxime Ripard wrote:
>
> > > +
> > > + ret = devm_gpio_request_one(&spi->dev, lcd->im_pins[i],
> > > + GPIOF_OUT_INIT_LOW, "im_pins");
> >
> > This makes a checkpatch warning such as 'WARNING: line over 80 characters'.
> > How about the following?
> >
> > ret = devm_gpio_request_one(&spi->dev, lcd->im_pins[i],
> > GPIOF_OUT_INIT_LOW, "im_pins");
>
> IIRC, some maintainers gripe (davem?) when they see such alignment,
> preferring the original arg below arg alignment vs strict 80 column.
As far as I know, the coding guide styles are quite fuzzy about this:
- The new line is not required to be aligned with the braces above
- Yet, the emacs config given does indent like this.
- 80 characters is said not to be a hard limit
I don't really know if there's a better solution here, except maybe:
ret = devm_gpio_request_one(&spi-dev, lcd->im_pins[i],
GPIOF_OUT_INIT_LOW,
"im_pins");
But it's not really a big deal, is it?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-19 8:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 15:26 [PATCH 0/3] Few ignored framebuffer fixes/additions Maxime Ripard
2013-07-15 15:26 ` Maxime Ripard
2013-07-15 15:26 ` Maxime Ripard
2013-07-15 15:27 ` [PATCH 1/3] video: mxsfb: fix color settings for 18bit data bus and 32bpp Maxime Ripard
2013-07-15 15:27 ` Maxime Ripard
2013-07-15 15:27 ` Maxime Ripard
2013-07-15 15:27 ` [PATCH 2/3] video: hx8357: Make IM pins optional Maxime Ripard
2013-07-15 15:27 ` Maxime Ripard
2013-07-15 15:27 ` Maxime Ripard
2013-07-16 0:49 ` Jingoo Han
2013-07-16 0:49 ` Jingoo Han
2013-07-16 0:49 ` Jingoo Han
2013-07-16 3:29 ` Mike Galbraith
2013-07-16 3:29 ` Mike Galbraith
2013-07-16 3:29 ` Mike Galbraith
2013-07-19 8:35 ` 'Maxime Ripard' [this message]
2013-07-19 8:35 ` 'Maxime Ripard'
2013-07-19 8:35 ` 'Maxime Ripard'
2013-07-22 8:30 ` Jingoo Han
2013-07-22 8:30 ` Jingoo Han
2013-07-22 8:30 ` Jingoo Han
2013-07-15 15:27 ` [PATCH 3/3] fb: backlight: HX8357: Add HX8369 support Maxime Ripard
2013-07-15 15:27 ` Maxime Ripard
2013-07-15 15:27 ` Maxime Ripard
2013-07-16 2:04 ` Jingoo Han
2013-07-16 2:04 ` Jingoo Han
2013-07-16 2:04 ` Jingoo Han
2013-07-16 15:46 ` 'Maxime Ripard'
2013-07-16 15:46 ` 'Maxime Ripard'
2013-07-16 15:46 ` 'Maxime Ripard'
2013-07-17 21:37 ` [PATCH 0/3] Few ignored framebuffer fixes/additions Andrew Morton
2013-07-17 21:37 ` Andrew Morton
2013-07-17 21:37 ` Andrew Morton
2013-07-19 8:27 ` Maxime Ripard
2013-07-19 8:27 ` Maxime Ripard
2013-07-19 8:27 ` Maxime Ripard
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=20130719083555.GC5106@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.