From: Li Yang <leoyang.li@nxp.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
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@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 1/4] ahci: qoriq: Add platform dependencies
Date: Fri, 22 May 2020 16:29:09 -0500 [thread overview]
Message-ID: <CADRPPNSwEv_SV4jQk-gOj6+WhAX1jVQk2szgPN=o2JVqV0yjLw@mail.gmail.com> (raw)
In-Reply-To: <20200507112955.23520-2-geert+renesas@glider.be>
On Thu, May 7, 2020 at 6:30 AM Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
>
> The Freescale QorIQ AHCI SATA controller is only present on Freescale
> Layerscape SoCs. Add platform dependencies to the AHCI_QORIQ config
> symbol, to avoid asking the user about it when configuring a kernel
> without Layerscape support.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Hi Jens,
Are you applying this patches? I can also apply it with your ACK.
Regards,
Leo
> ---
> drivers/ata/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/ata/Kconfig b/drivers/ata/Kconfig
> index 05ecdce1b702cf8b..d9e66b37acd1862a 100644
> --- a/drivers/ata/Kconfig
> +++ b/drivers/ata/Kconfig
> @@ -264,6 +264,7 @@ config AHCI_XGENE
> config AHCI_QORIQ
> tristate "Freescale QorIQ AHCI SATA support"
> depends on OF
> + depends on SOC_LS1021A || ARCH_LAYERSCAPE || COMPILE_TEST
> select SATA_HOST
> help
> This option enables support for the Freescale QorIQ AHCI SoC's
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-05-22 21:29 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 [this message]
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='CADRPPNSwEv_SV4jQk-gOj6+WhAX1jVQk2szgPN=o2JVqV0yjLw@mail.gmail.com' \
--to=leoyang.li@nxp.com \
--cc=amit.kucheria@verdurent.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=daniel.lezcano@linaro.org \
--cc=geert+renesas@glider.be \
--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).