From: Sam Ravnborg <sam@ravnborg.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Peter Foley <pefoley2@pefoley.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 1/4] Documentation: use subdir-y to avoid unnecessary built-in.o files
Date: Wed, 9 Jul 2014 22:52:20 +0200 [thread overview]
Message-ID: <20140709205219.GC32335@ravnborg.org> (raw)
In-Reply-To: <53AF78A7.8050106@infradead.org>
On Sat, Jun 28, 2014 at 07:23:35PM -0700, Randy Dunlap wrote:
> On 04/17/14 07:11, Peter Foley wrote:
> > Change the Documentation makefiles from obj-m to subdir-y
> > to avoid generating unnecessary built-in.o files since nothing
> > in Documentation/ is ever linked in to vmlinux.
> >
> > Signed-off-by: Peter Foley <pefoley2@pefoley.com>
>
> Hi Michal,
>
> Does this look good to you?
> I don't have enough makefile fu (or is it foo?) to judge this.
Looks OK.
Please add my:
Acked-by: Sam Ravnborg <sam@ravnborg.org>
Sam
next prev parent reply other threads:[~2014-07-09 20:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 14:11 [PATCH 1/4] Documentation: use subdir-y to avoid unnecessary built-in.o files Peter Foley
2014-04-17 14:11 ` [PATCH 2/4] Documentation: add makefiles for more targets Peter Foley
2014-08-26 16:50 ` Andrey Wagin
2014-04-17 14:11 ` [PATCH 3/4] Documentation: make functions static to avoid prototype warnings Peter Foley
2014-04-17 14:11 ` [PATCH 4/4] Documentation: fix misc. warnings Peter Foley
2014-06-29 2:23 ` [PATCH 1/4] Documentation: use subdir-y to avoid unnecessary built-in.o files Randy Dunlap
2014-07-09 20:52 ` Sam Ravnborg [this message]
2014-08-25 20:33 ` Randy Dunlap
2014-09-02 22:58 ` Peter Foley
2014-09-02 23:24 ` Randy Dunlap
2014-09-02 23:29 ` Mark Brown
2014-09-03 23:08 ` Peter Foley
2014-09-03 23:21 ` Mark Brown
2014-09-03 23:38 ` Randy Dunlap
2014-09-03 23:49 ` Mark Brown
2014-09-04 10:42 ` Mark Brown
2014-09-06 0:07 ` Randy Dunlap
2014-09-07 17:59 ` Randy Dunlap
2014-09-07 18:48 ` Mark Brown
2014-09-07 20:52 ` Randy Dunlap
2014-09-08 8:03 ` Stephen Rothwell
2014-09-08 10:22 ` Mark Brown
2014-09-08 14:57 ` Stephen Rothwell
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=20140709205219.GC32335@ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=pefoley2@pefoley.com \
--cc=rdunlap@infradead.org \
/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