From: Christoph Hellwig <hch@infradead.org>
To: Jeremy <jeremy.katz@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@osdl.org>, Linus <torvalds@osdl.org>,
linuxppc64-dev@lists.linuxppc.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PPC64 iSeries viodasd proc file
Date: Sun, 20 Jun 2004 22:11:43 +0100 [thread overview]
Message-ID: <20040620211143.GA8368@infradead.org> (raw)
In-Reply-To: <cb5afee1040620125272ab9f06@mail.gmail.com>
On Sun, Jun 20, 2004 at 03:52:33PM -0400, Jeremy wrote:
> It was in the tree for the platform, not just vendor trees. ie,
> anyone who wanted to use the platform with Linux would have had this
> functionality. If you'd argue that people shouldn't do that, then how
> are platforms supposed to get to a point where they can be included in
> the mainline tree?
Doesn't matter. There was a really crappy 2.4 driver that IBM didn't
even bother to submit. So for us it simply doesn't matter it existed.
Stop whining and ensure you're employer doesn't apply broken IBM patches
instead.
next prev parent reply other threads:[~2004-06-20 21:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 6:54 [PATCH] PPC64 iSeries viodasd proc file Stephen Rothwell
2004-06-18 15:09 ` Jeff Garzik
2004-06-18 15:17 ` Christoph Hellwig
2004-06-20 19:52 ` Jeremy
2004-06-20 21:11 ` Christoph Hellwig [this message]
2004-06-21 6:04 ` Greg KH
[not found] ` <cb5afee10406210914451dc6@mail.gmail.com>
2004-06-23 21:15 ` Jeremy Katz
2004-06-23 21:45 ` Jeff Garzik
2004-06-23 22:03 ` Greg KH
2004-06-24 0:38 ` Jeff Garzik
2004-06-24 20:59 ` Greg KH
2004-06-24 21:25 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-06-23 23:54 Stephen Rothwell
2004-06-23 23:55 ` Greg KH
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=20040620211143.GA8368@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=jeremy.katz@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@osdl.org \
/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