[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150429151147.GX9169@x1>
Date: Wed, 29 Apr 2015 16:11:47 +0100
From: Lee Jones <lee.jones@...aro.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Maxime Ripard <maxime.ripard@...e-electrons.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
kernel@...inux.com, Mike Turquette <mturquette@...aro.org>,
Stephen Boyd <sboyd@...eaurora.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH v6 4/4] clk: dt: Introduce binding for always-on clock
support
On Wed, 29 Apr 2015, Geert Uytterhoeven wrote:
> On Wed, Apr 29, 2015 at 4:17 PM, Lee Jones <lee.jones@...aro.org> wrote:
> > This useful binding should be accepted and people should not abuse
> > it. If they do and the vendor Maintainer's review and accept then
> > they have no foundation for recourse.
> >
> > Would you prefer it if I made the warning starker?
>
> Perhaps you can add a check for "clock-always-on" to scripts/checkpatch.pl,
> to make people aware they should think twice?
That's a really nice idea!
Maxime, would that make you happ(y|ier)?
> Nah, people don't read documentation, don't run checkpatch, ignore compiler
> warnings, etc...
:)
You can only wrap people in so much cotton wool. If they then decide
to ignore all the warnings and jump, woe betide them.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists