linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Maxime Ripard <maxime.ripard@free-electrons.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	kernel@stlinux.com, Mike Turquette <mturquette@linaro.org>,
	Stephen Boyd <sboyd@codeaurora.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v6 4/4] clk: dt: Introduce binding for always-on clock support
Date: Wed, 29 Apr 2015 16:33:11 +0200	[thread overview]
Message-ID: <CAMuHMdVdtoXGhK97Ky5hoVcjM6XZAZXKWELL64MFQebMpFr2Ng@mail.gmail.com> (raw)
In-Reply-To: <20150429141751.GR9169@x1>

Hi Lee,

On Wed, Apr 29, 2015 at 4:17 PM, Lee Jones <lee.jones@linaro.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?

Nah, people don't read documentation, don't run checkpatch, ignore compiler
warnings, etc...

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2015-04-29 14:33 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 18:43 [PATCH v6 0/4] clk: Provide support for always-on clocks Lee Jones
2015-04-07 18:43 ` [PATCH v6 1/4] ARM: sti: stih407-family: Supply defines for CLOCKGEN A0 Lee Jones
2015-04-07 18:43 ` [PATCH v6 2/4] ARM: sti: stih410-clocks: Identify critical clocks as always-on Lee Jones
2015-04-07 18:43 ` [PATCH v6 3/4] clk: Provide always-on clock support Lee Jones
2015-04-08  5:02   ` Stephen Boyd
2015-04-07 18:43 ` [PATCH v6 4/4] clk: dt: Introduce binding for " Lee Jones
2015-04-07 19:17   ` Maxime Ripard
2015-04-08  8:14     ` Lee Jones
2015-04-08  9:43       ` Maxime Ripard
2015-04-08 10:38         ` Lee Jones
2015-04-08 15:57           ` Maxime Ripard
2015-04-08 17:23             ` Lee Jones
2015-04-22  9:34               ` Maxime Ripard
2015-04-29 14:17                 ` Lee Jones
2015-04-29 14:33                   ` Geert Uytterhoeven [this message]
2015-04-29 15:11                     ` Lee Jones
2015-04-29 20:27                       ` Maxime Ripard
2015-04-29 14:51                   ` Sascha Hauer
2015-04-29 16:07                     ` Lee Jones
2015-04-29 23:05                       ` Michael Turquette
2015-05-04 13:31                         ` Maxime Ripard
2015-04-29 20:23                   ` Maxime Ripard
2015-04-30  9:57                     ` Lee Jones
2015-05-01  5:34                       ` Sascha Hauer
2015-05-01  6:44                         ` Lee Jones
2015-05-07 21:20                           ` Maxime Ripard
2015-05-08  7:22                             ` Lee Jones
2015-05-15 14:12                               ` Maxime Ripard
2015-04-07 20:32   ` Rob Herring
2015-04-08  5:25   ` Stephen Boyd
2015-04-08  5:28 ` [PATCH v6 0/4] clk: Provide support for always-on clocks Stephen Boyd

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=CAMuHMdVdtoXGhK97Ky5hoVcjM6XZAZXKWELL64MFQebMpFr2Ng@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@stlinux.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=mturquette@linaro.org \
    --cc=sboyd@codeaurora.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).