From: Roland McGrath <roland@redhat.com>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: Roland Dreier <rdreier@cisco.com>,
Tiago Maluta <tiago.maluta@gmail.com>,
Michal Marek <mmarek@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] Fix CONFIG_CROSS_COMPILE issue in .config
Date: Tue, 10 Aug 2010 00:33:17 -0700 (PDT) [thread overview]
Message-ID: <20100810073317.F2A8C40542@magilla.sf.frob.com> (raw)
In-Reply-To: Yegor Yefremov's message of Tuesday, 10 August 2010 08:43:18 +0200 <AANLkTikvRqTR6TjP9H4-_RHhax24YRPv9PCxn165RTWs@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown, Size: 543 bytes --]
> On Fri, Aug 6, 2010 at 12:26 AM, Roland McGrath <roland@redhat.com> wrote:
> >> Yes, this make sense to me. It's not clear to me why we ever needed
> >> the conditional assignment of an empty CROSS_COMPILE (that code predates
> >> the start of git history) [...]
> >
> > Perhaps someone used make --warn-undefined-variables.
>
> Are there any other comments or is the patch valid? Should I resend it
> as a new thread?
The patch is fine. The comments were just about how it might have gotten
to be how it was before now.
Thanks,
Roland
next prev parent reply other threads:[~2010-08-10 7:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTim2mi0wbJJl17OkbCJbRt-s5phR4sumn5GsJKUp@mail.gmail.com>
2010-06-21 19:06 ` [PATCH] Fix CONFIG_CROSS_COMPILE issue in .config Andrew Morton
2010-06-21 19:09 ` Roland McGrath
2010-06-21 19:54 ` Michal Marek
2010-06-23 3:44 ` Tiago Maluta
2010-08-04 12:16 ` Yegor Yefremov
2010-08-05 21:37 ` Roland Dreier
2010-08-05 22:26 ` Roland McGrath
2010-08-10 6:43 ` Yegor Yefremov
2010-08-10 7:33 ` Roland McGrath [this message]
2010-08-10 11:21 ` Michal Marek
2010-08-16 12:35 ` Andrew Hendry
2010-08-16 12:40 ` Michal Marek
2010-08-16 12:51 ` Andrew Hendry
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=20100810073317.F2A8C40542@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rdreier@cisco.com \
--cc=tiago.maluta@gmail.com \
--cc=yegorslists@googlemail.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