From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Douglas Anderson <dianders@chromium.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] soc: rockchip: ROCKCHIP_GRF should not default to y, unconditionally
Date: Fri, 16 Jul 2021 09:15:25 +0200 [thread overview]
Message-ID: <CAMuHMdUYLVHwb1EdLO0D-cAyJAvx=pjHHZNg1wDCmVu+nTBVKw@mail.gmail.com> (raw)
In-Reply-To: <162638886252.651069.16002951650407635275.b4-ty@sntech.de>
Hi Heiko,
On Fri, Jul 16, 2021 at 12:42 AM Heiko Stuebner <heiko@sntech.de> wrote:
> On Mon, 8 Feb 2021 15:38:55 +0100, Geert Uytterhoeven wrote:
> > Merely enabling CONFIG_COMPILE_TEST should not enable additional code.
> > To fix this, restrict the automatic enabling of ROCKCHIP_GRF to
> > ARCH_ROCKCHIP, and ask the user in case of compile-testing.
>
> Applied, thanks!
>
> [1/1] soc: rockchip: ROCKCHIP_GRF should not default to y, unconditionally
> commit: 2a1c55d4762dd34a8b0f2e36fb01b7b16b60735b
>
> I actually found the old one deep down in my inbox some days ago,
> so had applied that one already. Hope nothing changed with your
> RESEND.
They're identical, 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
_______________________________________________
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:[~2021-07-16 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 14:38 [PATCH] soc: rockchip: ROCKCHIP_GRF should not default to y, unconditionally Geert Uytterhoeven
2021-07-15 22:42 ` Heiko Stuebner
2021-07-16 7:15 ` 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='CAMuHMdUYLVHwb1EdLO0D-cAyJAvx=pjHHZNg1wDCmVu+nTBVKw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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).