linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
	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>
Cc: Amit Kucheria <amit.kucheria@verdurent.com>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-ide@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/4] qoriq: Add platform dependencies
Date: Thu,  7 May 2020 13:29:51 +0200	[thread overview]
Message-ID: <20200507112955.23520-1-geert+renesas@glider.be> (raw)

	Hi all,

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!

Geert Uytterhoeven (4):
  ahci: qoriq: Add platform dependencies
  cpufreq: qoriq: Add platform dependencies
  clk: qoriq: Add platform dependencies
  thermal: qoriq: Add platform dependencies

 drivers/ata/Kconfig     | 1 +
 drivers/clk/Kconfig     | 3 ++-
 drivers/cpufreq/Kconfig | 3 ++-
 drivers/thermal/Kconfig | 4 ++--
 4 files changed, 7 insertions(+), 4 deletions(-)

-- 
2.17.1

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:[~2020-05-07 11:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 11:29 Geert Uytterhoeven [this message]
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

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=20200507112955.23520-1-geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --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 \
    --subject='Re: [PATCH 0/4] qoriq: Add platform dependencies' \
    /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

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).