From: Michal Marek <mmarek@suse.cz>
To: Sam Ravnborg <sam@ravnborg.org>, Yann Droneaud <ydroneaud@opteya.com>
Cc: linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill@shutemov.name>,
David Woodhouse <dwmw2@infradead.org>,
Rob Landley <rob@landley.net>
Subject: Re: [PATCHv1 1/2] Documentation: headers_install.txt is part of kbuild
Date: Tue, 05 Aug 2014 16:08:59 +0200 [thread overview]
Message-ID: <53E0E57B.8010600@suse.cz> (raw)
In-Reply-To: <20140713211819.GA16496@ravnborg.org>
On 2014-07-13 23:18, Sam Ravnborg wrote:
> On Sun, Jul 13, 2014 at 12:15:29PM +0200, Yann Droneaud wrote:
>> 'headers_install.txt' from Documentation/make/ is related to Kbuild
>> so it must be moved in Documentation/kbuild/ directory.
>>
>> As Documentation/make/ directory has only one file, it will be removed
>> as a consequence of moving 'headers_install.txt'.
>>
>> Cc: Kirill A. Shutemov <kirill@shutemov.name>
>> Cc: Michal Marek <mmarek@suse.cz>
>> Cc: David Woodhouse <dwmw2@infradead.org>
>> Cc: Rob Landley <rob@landley.net>
>> Cc: Sam Ravnborg <sam@ravnborg.org>
>> Signed-off-by: Yann Droneaud <ydroneaud@opteya.com>
>
> This is much better - thanks.
> Acked-by: Sam Ravnborg <sam@ravnborg.org>
Applied to kbuild.git#misc, thanks.
Michal
next prev parent reply other threads:[~2014-08-05 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 19:11 [PATCH] Documentation/make/headers_install.txt: update documentation Yann Droneaud
2014-07-03 21:12 ` Michal Marek
2014-07-09 20:49 ` Sam Ravnborg
2014-07-13 10:15 ` [PATCHv1 0/2] Documentation: move and update headers_install.txt Yann Droneaud
2014-07-13 10:15 ` [PATCHv1 1/2] Documentation: headers_install.txt is part of kbuild Yann Droneaud
2014-07-13 21:18 ` Sam Ravnborg
2014-08-05 14:08 ` Michal Marek [this message]
2014-07-13 10:15 ` [PATCHv1 2/2] Documentation/kbuild/headers_install.txt: update documentation Yann Droneaud
2014-07-13 21:26 ` Sam Ravnborg
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=53E0E57B.8010600@suse.cz \
--to=mmarek@suse.cz \
--cc=dwmw2@infradead.org \
--cc=kirill@shutemov.name \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=sam@ravnborg.org \
--cc=ydroneaud@opteya.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