From: David Mosberger <davidm@napali.hpl.hp.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: davidm@hpl.hp.com, torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: bk pull
Date: Wed, 9 Apr 2003 13:49:58 -0700 [thread overview]
Message-ID: <16020.34678.824488.248372@napali.hpl.hp.com> (raw)
In-Reply-To: <20030409203836.A9397@infradead.org>
>>>>> On Wed, 9 Apr 2003 20:38:36 +0100, Christoph Hellwig <hch@infradead.org> said:
Christoph> Btw, do you have any plans to push the changes outside
Christoph> from arch/ia64 and include/asm-ia64/ in the ia64 patch to
Christoph> Linus? It would be really nice if the ia64 port could be
Christoph> used with an out-of-the-box kernel.
Boy, what a loaded question!
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.
Having said that, I do submit patches to the respective maintainers
quite frequently. I probably should cc linux-kernel more often so
others can see that. Anyhow, I think part of the problem is that I'm
simply not willing to spend inordinate amounts of time pushing the
patches (no, maintaining a kernel tree is not much fun and most
definitely underappreciated, so I do want to get some real work done
occasionally). For example, the sound driver patches have been around
forever, have been submitted multiple times, and each time we get a
"yeah, that looks good, let me work on it" and that's the last thing
we hear.
I think the only two biggies right now are the AGP/DRM changes (which
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... ;-)
--david
next prev parent reply other threads:[~2003-04-09 20:38 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 [this message]
2003-04-09 20:56 ` Christoph Hellwig
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=16020.34678.824488.248372@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=davidm@hpl.hp.com \
--cc=hch@infradead.org \
--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®