From: mmarek@suse•cz (Michal Marek)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC] Kbuild: allow code re-use across different directories
Date: Wed, 14 Sep 2011 03:48:35 +0200 [thread overview]
Message-ID: <4E7007F3.9080305@suse.cz> (raw)
In-Reply-To: <CACqU3MUfJAeur_65i5vDegu1d1VqAdq15EedfX9A3w52J23MPg@mail.gmail.com>
Dne 13.9.2011 23:13, Arnaud Lacombe napsal(a):
> 2011/9/9 Michal Marek <mmarek@suse•cz>:
>> On 20.8.2011 02:37, Arnaud Lacombe wrote:
>>> With the attached patch, we would do:
>>>
>>> arch/foo/boot/Makefile:
>>> LDFLAGS_fancy.o := -DPANTS=30
>>> obj-y += fancy.o
>>> vpath-y += $(srctree)/arch/foo/lib
>>>
>>> and let GNU make do the job.
>>
>> I like this. The only issue I can think of right now, is that if you add
>> a large directory to vpath-y, then it would be easy to accidentally
>> reuse more files from that directory than intended. But that could be
>> easily prevented by isolating those reusable source files.
>>
> I do not think it is that dangerous. We enforce unique access to VPATH
> and we still prioritize $(src) over any other specified path.
>
> That said, what would you want to pull the patch into -next, beside
> kernel.org being up ?
Just post it with a proper signoff. But there won't be any linux-next
until kernel.org is back again.
Michal
prev parent reply other threads:[~2011-09-14 1:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 0:37 [RFC] Kbuild: allow code re-use across different directories Arnaud Lacombe
2011-08-22 8:42 ` Cong Wang
2011-08-30 0:31 ` Arnaud Lacombe
2011-08-30 4:32 ` Nicolas Pitre
2011-08-30 4:36 ` Arnaud Lacombe
2011-09-07 19:07 ` Nicolas Pitre
2011-09-07 19:34 ` Arnaud Lacombe
2011-09-07 19:59 ` Nicolas Pitre
2011-09-07 20:52 ` Arnaud Lacombe
2011-09-08 4:50 ` Arnaud Lacombe
2011-09-08 20:33 ` Nicolas Pitre
2011-09-09 1:22 ` Arnaud Lacombe
2011-09-09 12:32 ` Michal Marek
2011-09-09 16:16 ` Arnaud Lacombe
2011-09-08 18:24 ` Arnaud Lacombe
2011-09-09 12:30 ` Michal Marek
2011-09-13 21:13 ` Arnaud Lacombe
2011-09-14 1:48 ` Michal Marek [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=4E7007F3.9080305@suse.cz \
--to=mmarek@suse$(echo .)cz \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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