From: Richard Weinberger <richard@nod.at>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
Nicholas Piggin <npiggin@gmail.com>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
david@sigma-star.at, kbuild-all@01.org,
Sam Ravnborg <sam@ravnborg.org>,
Arnaud Lacombe <lacombar@gmail.com>,
Nick Bowler <nbowler@elliptictech.com>,
Michal Marek <mmarek@suse.cz>, Nicolas Pitre <nico@linaro.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH v2] kbuild: Don't source kernel config
Date: Tue, 20 Feb 2018 17:55:51 +0100 [thread overview]
Message-ID: <2045626.ePW2a4dgOU@blindfold> (raw)
In-Reply-To: <CAK7LNARDG3TaMsSH__u9W_RmxcwrMZsrfn82L3Cf8Ec9N2jodg@mail.gmail.com>
Am Dienstag, 20. Februar 2018, 17:30:10 CET schrieb Masahiro Yamada:
> > That way the conf tool will sanitize the .config before shell scripts will
> > source it.
>
> This approach seems better.
Okay, let's go for it. :)
I went first for the ugly bash approach because it is a white list and not a
black list filter.
Thanks,
//richard
prev parent reply other threads:[~2018-02-20 16:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 9:22 [PATCH v2] kbuild: Don't source kernel config Richard Weinberger
2018-02-20 15:18 ` Masahiro Yamada
2018-02-20 15:25 ` Richard Weinberger
2018-02-20 16:00 ` Masahiro Yamada
2018-02-20 16:16 ` Richard Weinberger
2018-02-20 16:26 ` Nicolas Pitre
2018-02-20 16:30 ` Masahiro Yamada
2018-02-20 16:55 ` Richard Weinberger [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=2045626.ePW2a4dgOU@blindfold \
--to=richard@nod.at \
--cc=akpm@linux-foundation.org \
--cc=david@sigma-star.at \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=kstewart@linuxfoundation.org \
--cc=lacombar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=nbowler@elliptictech.com \
--cc=nico@linaro.org \
--cc=npiggin@gmail.com \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.org \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).