From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Herve Codina <herve.codina@bootlin.com>,
Li Yang <leoyang.li@nxp.com>, Mark Brown <broonie@kernel.org>,
Qiang Zhao <qiang.zhao@nxp.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>
Subject: Re: Question about the dependency on the config SOC_FSL in CPM_QMC
Date: Tue, 14 Mar 2023 07:57:47 +0000 [thread overview]
Message-ID: <49c46a72-ba18-2271-cd0b-5ef2af4639a3@csgroup.eu> (raw)
In-Reply-To: <CAKXUXMwwQuwssyzBrOXHOz__YRpa1Rjgqmwn5rRFjDVLBbabPA@mail.gmail.com>
Hi Lukas
Le 14/03/2023 à 08:21, Lukas Bulwahn a écrit :
> Dear Herve,
>
> In your patch below, you added the config CPM_QMC which depends on the
> non-existing config SOC_FSL:
>
> https://lore.kernel.org/r/20230217145645.1768659-7-herve.codina@bootlin.com
>
> Up to my knowledge, the config SOC_FSL never existed in the mainline
> tree. Is this dependency really required or can the expression simply
> be reduced to COMPILE_TEST and we drop the dependency to SOC_FSL?
That's a mistake, should be FSL_SOC.
See
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20230126083222.374243-7-herve.codina@bootlin.com/#3058690
Christophe
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-03-14 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 7:21 Question about the dependency on the config SOC_FSL in CPM_QMC Lukas Bulwahn
2023-03-14 7:57 ` Herve Codina
2023-03-14 8:17 ` Lukas Bulwahn
2023-03-14 7:57 ` Christophe Leroy [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=49c46a72-ba18-2271-cd0b-5ef2af4639a3@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=broonie@kernel.org \
--cc=herve.codina@bootlin.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukas.bulwahn@gmail.com \
--cc=qiang.zhao@nxp.com \
/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