All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Michal Marek <mmarek@suse.com>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v4] kbuild: trivial cleanups on the comments
Date: Wed, 2 Aug 2017 10:21:16 +0800	[thread overview]
Message-ID: <5981371C.5060108@cn.fujitsu.com> (raw)
In-Reply-To: <CAK7LNASx15Lw_fXhRwCDKjPo15_aD3du7EYhVXRAn4VcEcDd2A@mail.gmail.com>



On 08/02/2017 08:31 AM, Masahiro Yamada wrote:
> Hi.
> 
> 2017-08-01 20:36 GMT+09:00 Cao jin <caoj.fnst@cn.fujitsu.com>:
>> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
>> ---
>> Since this one has not been merged yet and I find more cleanups,
>> so I have v4 out.
>>
>> v3 addressed comments from Masahiro-san and Randy Dunlap.
>> v4 find several more cleanups in Makefile.build worth to be
>>    included into this trivial patch.
> 
> 
> OK, this is a collection of trivial fixes.
> 
> 
> While you are here, could you fix the following as well?
> 
> 
> [1]
> Makefile line 445:
> # Basic helpers built in scripts/
> 
>     scripts/   ->   scripts/basic/
> 
> 
> [2]
> Makefile line 508:
> # install and module_install need also be processed one by one
> 
> 
>    module_install  ->  modules_install
> 
> 

Sure, Masahiro-san, thanks for your reminding.

-- 
Sincerely,
Cao jin



      reply	other threads:[~2017-08-02  2:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01 11:36 [PATCH v4] kbuild: trivial cleanups on the comments Cao jin
2017-08-01 11:36 ` Cao jin
2017-08-02  0:31 ` Masahiro Yamada
2017-08-02  2:21   ` 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=5981371C.5060108@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=rdunlap@infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.