From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Olof Johansson <olof@lixom.net>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Russell King <linux@armlinux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
Kevin Hilman <khilman@baylibre.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: defconfig: Set CONFIG_LOCALVERSION in multi v4t/v5/v7 defconfigs
Date: Thu, 12 Jul 2018 09:25:15 +0200 [thread overview]
Message-ID: <CAMuHMdXZ8D2a-=z69US1=KEkqkrkbFqrR-zf-Suo5uaPYhSZSA@mail.gmail.com> (raw)
In-Reply-To: <CAOesGMgkU6yBRpAsED2fPyuAo9Tc=YprndGdkmBVrc+0783VwQ@mail.gmail.com>
Hi Olof,
On Wed, Jul 11, 2018 at 11:46 PM Olof Johansson <olof@lixom.net> wrote:
> On Wed, Jul 11, 2018 at 7:26 AM, Geert Uytterhoeven
> <geert+renesas@glider.be> wrote:
> > This allows to derive the kernel flavor from the kernel version at
> > runtime.
> >
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> I prefer not to have this go in -- this is extremely likely to creep
> into derivative configs and as such it would have no value (you can't
> be sure it's still the same config).
Fair enough. Unfortunately we cannot prevent that from happening :-(
> /proc/config.gz is the way to keep track of exactly what config you're
> running anyway, right?
Yes, in some convoluted and hard to identify way ;-)
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
prev parent reply other threads:[~2018-07-12 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 14:26 [PATCH] ARM: defconfig: Set CONFIG_LOCALVERSION in multi v4t/v5/v7 defconfigs Geert Uytterhoeven
2018-07-11 21:46 ` Olof Johansson
2018-07-12 7:25 ` 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='CAMuHMdXZ8D2a-=z69US1=KEkqkrkbFqrR-zf-Suo5uaPYhSZSA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=geert+renesas@glider.be \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=olof@lixom.net \
/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).