From: Michal Kubecek <mkubecek@suse.cz>
To: Chen-Yu Tsai <wens@csie.org>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk <linux-clk@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] clk: Add missing header for 'bool' definition to clk-conf.h
Date: Tue, 25 Aug 2015 08:59:32 +0200 [thread overview]
Message-ID: <20150825065932.GA29101@unicorn.suse.cz> (raw)
In-Reply-To: <CAGb2v67EhfgtbdLyFLd8xd6MMAnG4MGMvGLUTZxh=ag7XghvyA@mail.gmail.com>
On Tue, Aug 25, 2015 at 10:55:28AM +0800, Chen-Yu Tsai wrote:
> On Tue, Aug 25, 2015 at 5:28 AM, Stephen Boyd <sboyd@codeaurora.org> wrote:
> > On 08/18, Chen-Yu Tsai wrote:
> >> of_clk_set_defaults uses the type 'bool', but clk-conf.h does not
> >> include its definition.
> >>
> >> This results in a compile error when only clk-conf.h is used.
> >>
> >> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> >> Cc: stable@vger.kernel.org
> >
> > Why is stable Cc-ed? Is there some sort of compilation failure on
> > stable kernels?
>
> There isn't for now. Though I don't see why we shouldn't fix this for
> stable kernels as well. It's possible other people or third-party
> vendors working with stable/LTS kernels (Android?) may run into it.
How about
- It must fix a real bug that bothers people (not a, "This could be a
problem..." type thing).
in Documentation/stable_kernel_rules.txt?
Michal Kubecek
next prev parent reply other threads:[~2015-08-25 6:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 7:16 [PATCH] clk: Add missing header for 'bool' definition to clk-conf.h Chen-Yu Tsai
2015-08-24 21:28 ` Stephen Boyd
2015-08-25 2:55 ` Chen-Yu Tsai
2015-08-25 6:59 ` Michal Kubecek [this message]
2015-08-25 7:41 ` Chen-Yu Tsai
2015-08-25 17:53 ` 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=20150825065932.GA29101@unicorn.suse.cz \
--to=mkubecek@suse.cz \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=stable@vger.kernel.org \
--cc=wens@csie.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