From: Sam Ravnborg <sam@ravnborg.org>
To: Michal Marek <mmarek@suse.cz>
Cc: Yann Droneaud <ydroneaud@opteya.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org,
"Kirill A. Shutemov" <kirill@shutemov.name>,
David Woodhouse <dwmw2@infradead.org>,
Rob Landley <rob@landley.net>
Subject: Re: [PATCH] Documentation/make/headers_install.txt: update documentation
Date: Wed, 9 Jul 2014 22:49:15 +0200 [thread overview]
Message-ID: <20140709204915.GB32335@ravnborg.org> (raw)
In-Reply-To: <53B5C734.9020507@suse.cz>
On Thu, Jul 03, 2014 at 11:12:20PM +0200, Michal Marek wrote:
> Dne 30.6.2014 21:11, Yann Droneaud napsal(a):
> > Documentation in make/headers_install.txt is not
> > up to date regarding:
> > - way to list the various architectures;
> > - path where the headers are installed.
> >
> > This patch try to fix these issues.
> >
> > 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>
> > ---
> > Documentation/make/headers_install.txt | 15 ++++++++-------
>
> I have never noticed this file :). How about moving it to
> Documentation/kbuild?
Agree - please get this file moved.
Sam
next prev parent reply other threads:[~2014-07-09 20:49 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 [this message]
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
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=20140709204915.GB32335@ravnborg.org \
--to=sam@ravnborg.org \
--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=mmarek@suse.cz \
--cc=rob@landley.net \
--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;
as well as URLs for NNTP newsgroup(s).