From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Michal Marek <mmarek@suse.com>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Subject: Re: [PATCH 1/3] kbuild: call adjust_autoksyms.sh from source directory
Date: Mon, 25 Apr 2016 17:20:22 +0200 [thread overview]
Message-ID: <7296896.uWM0Bol2Ir@wuerfel> (raw)
In-Reply-To: <alpine.LFD.2.20.1604251015000.5091@knanqh.ubzr>
On Monday 25 April 2016 10:18:56 Nicolas Pitre wrote:
> On Mon, 25 Apr 2016, Arnd Bergmann wrote:
>
> > When building with separate object trees, scripts/adjust_autoksyms.sh
> > cannot be called from the object directory:
> >
> > /bin/bash: scripts/adjust_autoksyms.sh: No such file or directory
> >
> > This adds a $(src) prefix, as we do for all other shell scripts.
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> I posted fixes for all those problems already, plus another.
>
> You may grab them all at once from this branch where I committed them on
> top of Michal's kbuild branch:
>
> git://git.linaro.org/people/nicolas.pitre/linux kbuild
>
Ok, thanks!
I liked the idea of moving the samples from Documentation to samples,
but with your patches that is no longer required to fix the bug.
If the respective maintainers want to pick up my patches 2 and 3
independent of your fixes, I can rewrite the changelogs for those,
otherwise I'll just drop them all.
Arnd
next prev parent reply other threads:[~2016-04-25 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 13:17 Arnd Bergmann
2016-04-25 13:17 ` [PATCH 2/3] samples: connector: from Documentation to samples directory Arnd Bergmann
2016-04-25 13:17 ` [PATCH 3/3] samples: v4l: " Arnd Bergmann
2016-04-25 14:18 ` [PATCH 1/3] kbuild: call adjust_autoksyms.sh from source directory Nicolas Pitre
2016-04-25 15:20 ` Arnd Bergmann [this message]
2016-04-25 15:31 ` Nicolas Pitre
2016-04-25 16:03 ` Arnd Bergmann
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=7296896.uWM0Bol2Ir@wuerfel \
--to=arnd@arndb.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=mmarek@suse.com \
--cc=nicolas.pitre@linaro.org \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®