From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Michal Marek <mmarek@suse.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Top Makefile: tiny correction on `make help`
Date: Tue, 6 Jun 2017 16:51:14 +0800 [thread overview]
Message-ID: <59366D02.3020604@cn.fujitsu.com> (raw)
In-Reply-To: <CAK7LNAQ_OOvmCU6jdg+VNnWnZRzjeZ99Uz8o_2yDnMM+i=g=kg@mail.gmail.com>
Mr Masahiro,
On 06/06/2017 09:47 AM, Masahiro Yamada wrote:
> Hi Cao,
>
>
> 2017-05-29 12:21 GMT+09:00 Cao jin <caoj.fnst@cn.fujitsu.com>:
>> The help info of `make -C=1` is little confusing, make it clear.
>
> `make C=1` instead of `make -C=1`
>
>
>
>> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
>> ---
>> Makefile | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Makefile b/Makefile
>> index efa267a..b34a34d 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -1417,7 +1417,7 @@ help:
>> @echo ' make V=0|1 [targets] 0 => quiet build (default), 1 => verbose build'
>> @echo ' make V=2 [targets] 2 => give reason for rebuild of target'
>> @echo ' make O=dir [targets] Locate all output files in "dir", including .config'
>> - @echo ' make C=1 [targets] Check all c source with $$CHECK (sparse by default)'
>> + @echo ' make C=1 [targets] Check re-compiled c source only with $$CHECK (sparse by default)'
>> @echo ' make C=2 [targets] Force check of all c source with $$CHECK'
>> @echo ' make RECORDMCOUNT_WARN=1 [targets] Warn about ignored mcount sections'
>> @echo ' make W=n [targets] Enable extra gcc checks, n=1,2,3 where'
>
> Which phrase is qualified by "only"?
>
> [1] re-compiled c source only
> [2] only with $$CHECK
>
> I know [1] is what you mean (sorry for my nitpicking).
>
You are right, after reading it again, I myself have the same feeling as
you...
>
> Perhaps, "Check only re-compiled c source with $$CHECK" is even clearer?
>
> (or, just drop "only" because "re-compiled c source" is understandable enough ?)
I prefer the latter one.
>
>
> Could you use "kbuild: " instead of "Top Makefile" in the subject?
>
Sure.
Thanks very much for your suggestion:)
--
Sincerely,
Cao jin
prev parent reply other threads:[~2017-06-06 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 3:21 [PATCH] Top Makefile: tiny correction on `make help` Cao jin
2017-06-06 1:47 ` Masahiro Yamada
2017-06-06 8:51 ` Cao jin [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=59366D02.3020604@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.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