From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] [PATCH 04/10] pinctrl: sunxi: Wrap long compatible declaration lines
Date: Tue, 30 Jul 2013 22:31:15 +0200 [thread overview]
Message-ID: <20130730203115.GE12562@lukather> (raw)
In-Reply-To: <1375196953.32691.61.camel@kazak.uk.xensource.com>
Hi Ian,
On Tue, Jul 30, 2013 at 04:09:13PM +0100, Ian Campbell wrote:
> On Tue, 2013-07-30 at 16:59 +0200, Maxime Ripard wrote:
> > The compatible declaration and their associated data are exceeding the
> > 80-characters width limit.
> >
> > Split these lines to make them more readable and fit in the kernel
> > coding guidelines.
> >
> > Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> > Cc: Linus Walleij <linus.walleij@linaro.org>
> > ---
> > drivers/pinctrl/pinctrl-sunxi.c | 20 ++++++++++++++++----
> > 1 file changed, 16 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/pinctrl/pinctrl-sunxi.c b/drivers/pinctrl/pinctrl-sunxi.c
> > index 5985e60..246310b 100644
> > --- a/drivers/pinctrl/pinctrl-sunxi.c
> > +++ b/drivers/pinctrl/pinctrl-sunxi.c
> > @@ -628,10 +628,22 @@ static void sunxi_pinctrl_irq_handler(unsigned irq, struct irq_desc *desc)
> > }
> >
> > static struct of_device_id sunxi_pinctrl_match[] = {
> > - { .compatible = "allwinner,sun4i-a10-pinctrl", .data = (void *)&sun4i_a10_pinctrl_data },
> > - { .compatible = "allwinner,sun5i-a10s-pinctrl", .data = (void *)&sun5i_a10s_pinctrl_data },
> > - { .compatible = "allwinner,sun5i-a13-pinctrl", .data = (void *)&sun5i_a13_pinctrl_data },
> > - { .compatible = "allwinner,sun6i-a31-pinctrl", .data = (void *)&sun6i_a31_pinctrl_data },
> > + {
> > + .compatible = "allwinner,sun4i-a10-pinctrl",
> > + .data = (void *)&sun4i_a10_pinctrl_data,
> > + },
>
> I'm not sure this is actually an improvement, the original reads quite
> naturally even if it is a little long. What about a #define such that
> you can write:
> COMPAT("allwinner,sun4i-a10-pinctrl", sun4i_a10_pinctrl_data),
> and thereby stay within 80-chars?
>
> If you wanted to go overboard you could code the macro such that:
> SUNXI_COMPAT(sun4i,a10),
> expanded to what you want, that's pretty obfuscated though.
To be honest, I'm not convinced by any of the constructs seen above. The
one we had is too long, the 4-lines one is not that great either, and
the macro only obfuscates things away.
You know what, I'll drop this patch.
Thanks!
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/20130730/5afa76e1/attachment.sig>
next prev parent reply other threads:[~2013-07-30 20:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 14:59 [PATCH 00/10] Introduce Allwinner A20 support Maxime Ripard
2013-07-30 14:59 ` [PATCH 01/10] ARM: sunxi: " Maxime Ripard
2013-07-30 14:59 ` [PATCH 02/10] ARM: sun7i: Add Allwinner A20 DTSI Maxime Ripard
2013-07-30 14:59 ` [PATCH 03/10] ARM: sun7i: Add Olimex A20-Olinuxino-Micro support Maxime Ripard
2013-07-30 14:59 ` [PATCH 04/10] pinctrl: sunxi: Wrap long compatible declaration lines Maxime Ripard
2013-07-30 15:09 ` [linux-sunxi] " Ian Campbell
2013-07-30 20:31 ` Maxime Ripard [this message]
2013-07-30 14:59 ` [PATCH 05/10] pinctrl: sunxi: Add Allwinner A20 pins set Maxime Ripard
2013-07-30 14:59 ` [PATCH 06/10] pinctrl: sunxi: Fix inconsistent indentation Maxime Ripard
2013-07-30 14:59 ` [PATCH 07/10] ARM: sun7i: Add the PIO controller node to the DTSI Maxime Ripard
2013-07-30 14:59 ` [PATCH 08/10] ARM: sun7i: DT: Add UART muxing options " Maxime Ripard
2013-07-30 19:07 ` Sergei Shtylyov
2013-07-30 20:10 ` Maxime Ripard
2013-07-30 14:59 ` [PATCH 09/10] ARM: sun7i: a20-olinuxino: Enable UARTs muxing Maxime Ripard
2013-07-30 14:59 ` [PATCH 10/10] ARM: sun7i: a20-olinuxino: Enable the user LED 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=20130730203115.GE12562@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).