From: Michal Marek <mmarek@suse.cz>
To: Masahiro Yamada <yamada.m@jp.panasonic.com>,
linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: trivial - fix the help doc of CONFIG_CC_OPTIMIZE_FOR_SIZE
Date: Thu, 08 Jan 2015 14:54:21 +0100 [thread overview]
Message-ID: <54AE8C0D.2060007@suse.cz> (raw)
In-Reply-To: <20141211104609.A487.AA925319@jp.panasonic.com>
On 2014-12-11 02:46, Masahiro Yamada wrote:
> Hi Michal,
>
> Does this seem OK?
>
>
>
> On Tue, 5 Aug 2014 14:43:07 +0900
> Masahiro Yamada <yamada.m@jp.panasonic.com> wrote:
>
>> Other than GCC, we have another choice, Clang for building the kernel
>> these days. It seems better to say "compiler" rather than "gcc".
>>
>> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
Applied now, sorry for the delay.
Michal
prev parent reply other threads:[~2015-01-08 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 5:43 [PATCH] kbuild: trivial - fix the help doc of CONFIG_CC_OPTIMIZE_FOR_SIZE Masahiro Yamada
2014-12-11 1:46 ` Masahiro Yamada
2015-01-08 13:54 ` Michal Marek [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=54AE8C0D.2060007@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yamada.m@jp.panasonic.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