[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNARvsUB1a0LJvtJXKZZv2fiHAMrojKbF82--C4yQs=k35w@mail.gmail.com>
Date: Tue, 6 Aug 2019 18:35:06 +0900
From: Masahiro Yamada <yamada.masahiro@...ionext.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Sam Ravnborg <sam@...nborg.org>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
bpf@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Networking <netdev@...r.kernel.org>,
Amit Pundir <amit.pundir@...aro.org>
Subject: Re: [RFC PATCH] kbuild: re-implement detection of CONFIG options
leaked to user-space
Hi Arnd,
On Tue, Aug 6, 2019 at 6:00 PM Arnd Bergmann <arnd@...db.de> wrote:
>
> On Tue, Aug 6, 2019 at 6:38 AM Masahiro Yamada
> <yamada.masahiro@...ionext.com> wrote:
> >
> > I was playing with sed yesterday, but the resulted code might be unreadable.
> >
> > Sed scripts tend to be somewhat unreadable.
> > I just wondered which language is appropriate for this?
> > Maybe perl, or what else? I am not good at perl, though.
>
> I like the sed version, in particular as it seems to do the job and
> I'm not volunteering to write it in anything else.
>
> > Maybe, it will be better to fix existing warnings
> > before enabling this check.
>
> Yes, absolutely.
>
> > If somebody takes a closer look at them, that would be great.
>
> Let's see:
Thanks for looking into these!
If possible, could you please send patches to fix them?
We can start with low-hanging fruits to reduce the number of warnings.
Thank you.
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists