From: Dan Carpenter <dan.carpenter@oracle.com>
To: Martin Kelly <martin@martingkelly.com>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-kbuild@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-embedded@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
Matt Mackall <mpm@selenic.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools: fix cross-compile var export
Date: Mon, 8 Jan 2018 14:45:53 +0300 [thread overview]
Message-ID: <20180108114553.37buovfs7qimokzq@mwanda> (raw)
In-Reply-To: <c021c0f9-4504-6323-98ed-455a196463fc@martingkelly.com>
On Sun, Jan 07, 2018 at 10:51:21AM -0800, Martin Kelly wrote:
> Urg, I accidentally sent to kernel-kbuild instead of linux-kbuild, changed
> now. It appears that past changes to tools/scripts/Makefile.include have
> been handled by linux-kbuild and often Masahiro Yamada.
>
> Perhaps the best sequence here is to send a patch to kbuild adding the
> call-override function and calls to it to the main common Makefile. Then I
> can send individual subsystem patches dropping the individual CC = lines and
> similar. It will be 13 patches instead of 1 but will eventually result in
> the same thing.
>
> Paul, any thoughts?
>
That sounds good.
regards,
dan carpenter
next prev parent reply other threads:[~2018-01-08 11:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 20:16 [PATCH] tools: fix cross-compile var export Martin Kelly
2018-01-07 16:11 ` Paul Gortmaker
2018-01-07 18:31 ` Martin Kelly
2018-01-07 18:51 ` Martin Kelly
2018-01-08 11:45 ` Dan Carpenter [this message]
2018-01-07 19:04 ` Paul Gortmaker
2018-01-07 21:43 ` Martin Kelly
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=20180108114553.37buovfs7qimokzq@mwanda \
--to=dan.carpenter@oracle.com \
--cc=dwmw2@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@martingkelly.com \
--cc=michal.lkml@markovi.net \
--cc=mpm@selenic.com \
--cc=paul.gortmaker@windriver.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).