From: Will Deacon <will.deacon@arm.com>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: Lucas Stach <l.stach@pengutronix.de>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: Kconfig.platforms: fix warning unmet direct dependencies
Date: Wed, 30 Jan 2019 18:21:48 +0000 [thread overview]
Message-ID: <20190130182148.GO18558@fuggles.cambridge.arm.com> (raw)
In-Reply-To: <20190130084321.GB3369@localhost.localdomain>
On Wed, Jan 30, 2019 at 09:43:21AM +0100, Anders Roxell wrote:
> On 2019-01-25 16:57, Lucas Stach wrote:
> > Am Freitag, den 25.01.2019, 14:32 +0000 schrieb Catalin Marinas:
> > > On Tue, Jan 15, 2019 at 08:18:39PM +0100, Anders Roxell wrote:
> > > > When ARCH_MXC get enabled, ARM64_ERRATUM_845719 will be selected and
> > > > this warning will happen when COMPAT isn't set.
> > > >
> > > > WARNING: unmet direct dependencies detected for ARM64_ERRATUM_845719
> > > > Depends on [n]: COMPAT [=n]
> > > > Selected by [y]:
> > > > - ARCH_MXC [=y]
> > > >
> > > > Rework to add 'if COMPAT' before ARM64_ERRATUM_845719 gets selected,
> > > > since ARM64_ERRATUM_845719 depends on COMPAT.
> > > >
> > > > > > Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
> > > > ---
> > > > arch/arm64/Kconfig.platforms | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> > > > index 251ecf34cb02..d4faca775d9c 100644
> > > > --- a/arch/arm64/Kconfig.platforms
> > > > +++ b/arch/arm64/Kconfig.platforms
> > > > @@ -145,7 +145,7 @@ config ARCH_MVEBU
> > > > config ARCH_MXC
> > > > > > bool "ARMv8 based NXP i.MX SoC family"
> > > > > > select ARM64_ERRATUM_843419
> > > > > > - select ARM64_ERRATUM_845719
> > > > > > + select ARM64_ERRATUM_845719 if COMPAT
> > > > > > help
> > > > > > This enables support for the ARMv8 based SoCs in the
> > > > NXP i.MX family.
> > >
> > > Actually, do we need to select the errata workarounds explicitly? That
> > > seems to be the only case where we do it (commit 930507c18304, "arm64:
> > > add basic Kconfig symbols for i.MX8"). They are default y, so we
> > > shouldn't need to force them on.
> >
> > This is based on past experience. We've had a lot of cases were people
> > did not enable the necessary CPU errata workaround, which then usually
> > lead to very hard to debug system failures. It is on our list of things
> > to look out for now, but I would feel much better if there is just no
> > chance for a user to misconfigure the kernel in this way.
> >
>
> Would a better approach be to remove the 'depends on COMPAT' in the
> Kconfig and move it into the src files instead see below.
I'd prefer to keep the dependency here, because the erratum is not
applicable for native (64-bit) userspace.
I think your original patch is fine, so:
Acked-by: Will Deacon <will.deacon@arm.com>
Will
prev parent reply other threads:[~2019-01-30 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 19:18 Anders Roxell
2019-01-25 14:32 ` Catalin Marinas
2019-01-25 15:57 ` Lucas Stach
2019-01-30 8:43 ` Anders Roxell
2019-01-30 18:21 ` Will Deacon [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=20190130182148.GO18558@fuggles.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=anders.roxell@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®