[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <796bc082-7708-172e-df1e-13447ef6b577@web.de>
Date: Thu, 22 Aug 2019 13:00:52 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Matthias Maennich <maennich@...gle.com>, cocci@...teme.lip6.fr,
kernel-janitors@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Julia Lawall <Julia.Lawall@...6.fr>,
Martijn Coenen <maco@...roid.com>, linux-arch@...r.kernel.org,
linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-m68k@...ts.linux-m68k.org, linux-modules@...r.kernel.org,
linux-scsi@...r.kernel.org, linux-usb@...r.kernel.org,
kernel-team@...roid.com, usb-storage@...ts.one-eyed-alien.net,
x86@...nel.org, Alan Stern <stern@...land.harvard.edu>,
Arnd Bergmann <arnd@...db.de>,
"David S. Miller" <davem@...emloft.net>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Gilles Muller <Gilles.Muller@...6.fr>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
Jessica Yu <jeyu@...nel.org>,
Joel Fernandes <joel@...lfernandes.org>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Kate Stewart <kstewart@...uxfoundation.org>,
Lucas De Marchi <lucas.de.marchi@...il.com>,
Martijn Coenen <maco@...gle.com>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Mauro Carvalho Chehab <mchehab+samsung@...nel.org>,
Michal Marek <michal.lkml@...kovi.net>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Nicolas Palix <nicolas.palix@...g.fr>,
Oliver Neukum <oneukum@...e.com>,
Philippe Ombredanne <pombredanne@...b.com>,
Sam Ravnborg <sam@...nborg.org>,
Sandeep Patil <sspatil@...gle.com>,
Stephen Boyd <sboyd@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [v2 08/10] scripts: Coccinelle script for namespace dependencies
> $srctree is defined by kbuild in the toplevel Makefile.
How is this variable passed to the file “scripts/nsdeps”?
>> * Would you like to support a separate build directory for desired adjustments?
>
> No, as the purpose of this script is to directly patch the kernel
> sources where applicable.
Will there occasionally be a need to provide a generated patch
(without in-place file modification)?
>> I suggest to assign the name for the temporary file to a variable
>> which should be used by subsequent commands.
>
> I somehow don't agree that this is an improvement to the code as the
> variable would likely be something like ${source_file_tmp}.
Would you dare to choose a shorter variable name?
> ${source_file}.tmp does express the intent of a temporary file next to
> the original source file and the reader of the code does not need to
> reason about the value of ${source_file_tmp}.
I would find a code variant with less suffix repetition nicer.
Regards,
Markus
Powered by blists - more mailing lists