From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Li Yang <leoyang.li@nxp.com>
Cc: Shawn Guo <shawnguo@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Zhang Rui <rui.zhang@intel.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amit.kucheria@verdurent.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-ide@vger.kernel.org, linux-clk <linux-clk@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] qoriq: Add platform dependencies
Date: Fri, 8 May 2020 11:50:17 +0200 [thread overview]
Message-ID: <CAMuHMdXvHwZ88hhLzKcEW-tFCFiGdWBaABrirG3k1a9Y1=M_2w@mail.gmail.com> (raw)
In-Reply-To: <CADRPPNTdv3R4t7JsjGuPP5h5APA7vcSMNK1vJMjzPtGw=Uw9-w@mail.gmail.com>
Hi Li,
On Thu, May 7, 2020 at 11:58 PM Li Yang <leoyang.li@nxp.com> wrote:
> On Thu, May 7, 2020 at 6:31 AM Geert Uytterhoeven
> <geert+renesas@glider.be> wrote:
> > Several QorIQ blocks are only present on Freescale or NXP SoCs.
> > This series adds platform dependencies to the corresponding config
> > ymbols, to avoid asking the user about them when configuring a kernel
> > without support for these SoCs.
> >
> > Most patches in this series are independent, but the third patch may
> > cause some Kconfig warnings when applied before the second patch, and
> > enabling the QorIQ CPU frequency scaling driver in a non-Layerscape
> > kernel.
> >
> > Thanks for your comments!
>
> Thanks. The series looks good to me.
>
> Are we trying to merge them through the various driver subsystems or I
> can also pull them in through the fsl-soc tree. If we want to go
> through driver subsystems:
"fsl-soc" is safest, if maintainers agree, due to the weak dependency the
randconfig people may notice.
Note that Viresh already applied the 2nd patch to the cpufreq tree.
> Acked-by: Li Yang <leoyang.li@nxp.com>
Thanks!
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
prev parent reply other threads:[~2020-05-08 9:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 11:29 [PATCH 0/4] qoriq: Add platform dependencies Geert Uytterhoeven
2020-05-07 11:29 ` [PATCH 1/4] ahci: " Geert Uytterhoeven
2020-05-22 21:29 ` Li Yang
2020-05-07 11:29 ` [PATCH 2/4] cpufreq: " Geert Uytterhoeven
2020-05-08 5:23 ` Viresh Kumar
2020-05-07 11:29 ` [PATCH 3/4] clk: " Geert Uytterhoeven
2020-05-22 21:28 ` Li Yang
2020-05-07 11:29 ` [PATCH 4/4] thermal: " Geert Uytterhoeven
2020-05-22 16:57 ` Daniel Lezcano
2020-05-07 13:24 ` [PATCH 0/4] " Arnd Bergmann
2020-05-07 21:57 ` Li Yang
2020-05-08 9:50 ` Geert Uytterhoeven [this message]
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='CAMuHMdXvHwZ88hhLzKcEW-tFCFiGdWBaABrirG3k1a9Y1=M_2w@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=amit.kucheria@verdurent.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=daniel.lezcano@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=viresh.kumar@linaro.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).