From: Thierry Reding <thierry.reding@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/gdb: Use $(abspath ...) instead of $(shell cd ... && pwd)
Date: Mon, 18 Apr 2016 17:33:18 +0200 [thread overview]
Message-ID: <20160418153318.GC22979@ulmo.ba.sec> (raw)
In-Reply-To: <570B2260.90704@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
On Sun, Apr 10, 2016 at 09:04:48PM -0700, Jan Kiszka wrote:
> On 2016-04-08 02:16, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > Avoid forking off a shell to resolve the absolute path of the output
> > directory when make's builtin $(abspath ...) function will do an
> > adequate job.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> > scripts/gdb/linux/Makefile | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/scripts/gdb/linux/Makefile b/scripts/gdb/linux/Makefile
> > index 6cf1ecf61057..d8b88e22e16a 100644
> > --- a/scripts/gdb/linux/Makefile
> > +++ b/scripts/gdb/linux/Makefile
> > @@ -1,6 +1,6 @@
> > always := gdb-scripts
> >
> > -SRCTREE := $(shell cd $(srctree) && /bin/pwd)
> > +SRCTREE := $(abspath $(srctree))
> >
> > $(obj)/gdb-scripts:
> > ifneq ($(KBUILD_SRC),)
> >
>
> Thanks, good cleanup. Queued.
You might want to remove this, if it's not too late yet. I posted
another similar thread and people objected to it because it requires
GNU make 3.81, whereas the kernel build process officially still
supports 3.80.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-18 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 9:16 [PATCH] scripts/gdb: Use $(abspath ...) instead of $(shell cd ... && pwd) Thierry Reding
2016-04-11 4:04 ` Jan Kiszka
2016-04-18 15:33 ` Thierry Reding [this message]
2016-04-18 15:51 ` Jan Kiszka
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=20160418153318.GC22979@ulmo.ba.sec \
--to=thierry.reding@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-kernel@vger.kernel.org \
/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