From: "George Spelvin" <linux@horizon.com>
To: rdunlap@infradead.org, sam@ravnborg.org
Cc: linux-kbuild@vger.kernel.org, linux@horizon.com, mmarek@suse.cz,
yann.morin.1998@free.fr
Subject: Re: [PATCH] Documentation/kbuild/makefiles.txt: Improve description of lib-* targets
Date: 16 May 2014 06:32:02 -0400 [thread overview]
Message-ID: <20140516103202.11272.qmail@ns.horizon.com> (raw)
In-Reply-To: <20140516101433.GB10187@ravnborg.org>
>> On 05/10/2014 10:02 PM, George Spelvin wrote:
>>> - For consistency, objects listed in lib-m will be included in lib.a.
>>> +
>>> + For consistency, objects listed in lib-m will be included
>>> + in lib.a, but this will probably not do what you want.
Sam Ravneborg wrote:
> So maybe we should catch this and error out?
Given my current poor state of knowledge, that does indeed seem
like a better solution; I can't imagine a situation where the current
behavior is useful.
But can we not stall a straightforward and harmless documentation
upgrade waiting for a more ambitious solution? A significant
change to kbuild like that is going to trigger a (beneficial, but
slow) wave of bug reports and Kconfig/Makefile fixes.
next prev parent reply other threads:[~2014-05-16 10:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 2:24 Searching for insight into lib-y and lib-m George Spelvin
2014-05-11 4:28 ` Randy Dunlap
2014-05-11 5:02 ` [PATCH] Documentation/kbuild/makefiles.txt: Improve description of lib-* targets George Spelvin
2014-05-14 21:21 ` Randy Dunlap
2014-05-16 10:14 ` Sam Ravnborg
2014-05-16 10:32 ` George Spelvin [this message]
2014-06-10 12:47 ` Michal Marek
2014-06-08 4:35 ` George Spelvin
2014-05-11 12:34 ` Searching for insight into lib-y and lib-m Tejun Heo
2014-05-11 7:31 ` 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=20140516103202.11272.qmail@ns.horizon.com \
--to=linux@horizon.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rdunlap@infradead.org \
--cc=sam@ravnborg.org \
--cc=yann.morin.1998@free.fr \
/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