From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: yamada.masahiro@socionext.com
Cc: sergey.senozhatsky.work@gmail.com, linux-kernel@vger.kernel.org,
sergey.senozhatsky@gmail.com
Subject: Re: [next] kbuild: use $(srctree) instead of KBUILD_SRC to check out-of-tree build
Date: Fri, 19 Apr 2019 21:33:26 +0900 [thread overview]
Message-ID: <20190419123326.GA476@tigerII.localdomain> (raw)
In-Reply-To: <43c5127830dd44e0817c2aa1906fe515@SOC-EX01V.e01.socionext.com>
On (04/19/19 08:59), yamada.masahiro@socionext.com wrote:
> > It seems that commit a9a49c2ad9b9b8 (linux-next) breaks ./scripts/tags.sh
> > on my system. It scans, basically, my entire drive now (including the
> > root partition):
> >
> > $ ./scripts/tags.sh tags
>
> I did not know this script is run directly
> because I expected people were using 'make tags'.
:) I always run it directly, didn't even know there was 'make tags'
> It is easy to fix, though.
Works fine.
Tested-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
-ss
prev parent reply other threads:[~2019-04-19 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 8:33 [next] kbuild: use $(srctree) instead of KBUILD_SRC to check out-of-tree build Sergey Senozhatsky
2019-04-19 8:59 ` yamada.masahiro
2019-04-19 12:33 ` Sergey Senozhatsky [this message]
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=20190419123326.GA476@tigerII.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=yamada.masahiro@socionext.com \
/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