From: Christoph Hellwig <hch@infradead.org>
To: davidm@hpl.hp.com
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: bk pull
Date: Wed, 9 Apr 2003 21:56:50 +0100 [thread overview]
Message-ID: <20030409215650.A10311@infradead.org> (raw)
In-Reply-To: <16020.34678.824488.248372@napali.hpl.hp.com>; from davidm@napali.hpl.hp.com on Wed, Apr 09, 2003 at 01:49:58PM -0700
On Wed, Apr 09, 2003 at 01:49:58PM -0700, David Mosberger wrote:
> Sure, I too would like it if the kernel would always build
> out-of-the-box, but I don't think it's very realistic. Even if I
> followed Linus's checkins on an hourly basis (no way in hell I'm ever
> gonna do that), there is always a chance that he'll accept a patch
> that will (perhaps subtly) break non-x86 platforms.
Hey, I didn't mean _always_ build out of the box :) I'm much more
looking forward to 2.6.x releases I'd like to see just build for ia64.
> I'm working on) and the virtual mem_map support. The latter I haven't
> pushed at all so far, mostly because I just haven't had the
> time/energy/interest to do so. Also, I'm always optimistic someone
> else comes along to help with the work... ;-)
Well, I could try to help pushing some stuff. OTOH pushing stuff I
don't understand is a bad idea. Could you please explain e.g. the
mm/bootmem.c and mm/page_alloc.c changes?
next prev parent reply other threads:[~2003-04-09 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 19:27 David Mosberger
2003-04-09 19:38 ` Christoph Hellwig
2003-04-09 20:49 ` David Mosberger
2003-04-09 20:56 ` Christoph Hellwig [this message]
2003-04-09 22:23 ` David Mosberger
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=20030409215650.A10311@infradead.org \
--to=hch@infradead.org \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®