[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgweH9GibJBzuEZNBGKbYPrs4NchT0YLuyxk1=N7gsWog@mail.gmail.com>
Date: Thu, 27 Oct 2022 12:49:22 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Pavel Machek <pavel@...x.de>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Guenter Roeck <linux@...ck-us.net>, stable@...r.kernel.org,
patches@...ts.linux.dev, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org, shuah@...nel.org, patches@...nelci.org,
lkft-triage@...ts.linaro.org, jonathanh@...dia.com,
f.fainelli@...il.com, sudipm.mukherjee@...il.com,
srw@...dewatkins.net
Subject: Re: [PATCH 5.10 00/79] 5.10.151-rc1 review
On Thu, Oct 27, 2022 at 12:27 PM Pavel Machek <pavel@...x.de> wrote:
>
> Alternatively you can modify the caller to do /bin/sh /scripts/... so
> it does not need a +x bit...
Generally we should be doing both.
Make it have the proper +x bit to show clearly that it's an executable
script and have 'ls' and friends show it that way when people enable
colorization or whatever.
*And* make any Makefiles and tooling use an explicit "sh" or whatever
thing, because we've traditionally let people use tar-files and patch
to generate their trees, and various stupid tools exist and get it
wrong even when we get it right in our git tree.
So belt and suspenders.
But in this case, I think our tools already do the "run shell" part:
Makefile:PAHOLE_FLAGS = $(shell PAHOLE=$(PAHOLE)
$(srctree)/scripts/pahole-flags.sh)
no? And at least in my -git tree, it's already executable.
Maybe one of those "various stipid tools exists" is in the stable
tree. I didn't check.
Linus
Powered by blists - more mailing lists