From: Christoph Hellwig <hch@lst.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: jes@wildopensource.com, netdev@oss.sgi.com
Subject: Re: [PATCH] kill acient compat cruft from acenic
Date: Fri, 27 Feb 2004 21:57:29 +0100 [thread overview]
Message-ID: <20040227205729.GB20398@lst.de> (raw)
In-Reply-To: <403FAECD.3090203@pobox.com>
On Fri, Feb 27, 2004 at 03:55:41PM -0500, Jeff Garzik wrote:
> Christoph Hellwig wrote:
> >Kills lots of really old cruft and adds a little cruft to actually
> >make the driver work with recent 2.4 again.
>
>
> Since kcompat (http://sf.net/projects/gkernel/) lets PCI API drivers
> work in 2.2, 2.4 and 2.6, I am OK with applying this patch......
> assuming there is a second patch coming to convert to pci_driver API.
Jes said he doesn't care for 2.2 and early 2.4 anymore which makes life
much easier without external compat cruft.
As soon as this patch is in Linus' tree I'll send you a followup.
next prev parent reply other threads:[~2004-02-27 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 20:25 [PATCH] kill acient compat cruft from acenic Christoph Hellwig
2004-02-27 20:55 ` Jeff Garzik
2004-02-27 20:57 ` Christoph Hellwig [this message]
2004-02-27 20:58 ` Jeff Garzik
2004-02-28 18:27 ` Jes Sorensen
2004-02-28 18:29 ` Christoph Hellwig
2004-02-29 19:10 ` Jes Sorensen
2004-02-29 18:29 ` Jeff Garzik
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=20040227205729.GB20398@lst.de \
--to=hch@lst.de \
--cc=jes@wildopensource.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).