From: Arjan van de Ven <arjan@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ken Chen <kenchen@google.com>, Adam Litke <agl@us.ibm.com>,
William Lee Irwin III <wli@holomorphy.com>,
Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] rfc: introduce /dev/hugetlb
Date: Sun, 25 Mar 2007 12:22:29 +0200 [thread overview]
Message-ID: <1174818149.1158.301.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20070323205810.3860886d.akpm@linux-foundation.org>
> But libraries are hard, for a number of distributional reasons.
I don't see why this is the case to be honest.
You can ask distros to ship your library, and if it's a sensible one,
they will. And if you can't wait, you can always bundle the library with
your application, it's really not a big deal to do that properly.
That's not a reason to make it a harder problem by tying a library to
the kernel source... in fact I know enterprise distros are more likely
to uprev a library than to uprev a kernel.... tying them together you
get the worst of both worlds....
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2007-03-25 10:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 8:44 Ken Chen
2007-03-23 15:03 ` William Lee Irwin III
2007-03-23 21:56 ` Ken Chen
2007-03-23 15:03 ` Mel Gorman
2007-03-23 15:09 ` William Lee Irwin III
2007-03-23 15:15 ` Mel Gorman
2007-03-23 15:30 ` William Lee Irwin III
2007-03-23 22:04 ` Ken Chen
2007-03-23 21:08 ` Benjamin Herrenschmidt
2007-03-24 4:58 ` Andrew Morton
2007-03-24 5:32 ` Nish Aravamudan
2007-03-24 6:12 ` Andrew Morton
2007-03-24 6:57 ` Sam Ravnborg
2007-03-24 7:41 ` Andrew Morton
2007-03-24 7:11 ` Ken Chen
2007-03-24 7:39 ` Andrew Morton
2007-03-25 10:22 ` Arjan van de Ven [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=1174818149.1158.301.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wli@holomorphy.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