From: Christoph Hellwig <hch@lst.de>
To: Jes Sorensen <jes@wildopensource.com>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] kill ancient compat cruft from acenic
Date: Wed, 21 Jan 2004 10:47:14 +0100 [thread overview]
Message-ID: <20040121094714.GA20425@lst.de> (raw)
In-Reply-To: <yq065f566m6.fsf@wildopensource.com>
On Wed, Jan 21, 2004 at 03:36:17AM -0500, Jes Sorensen wrote:
> >>>>> "Christoph" == Christoph Hellwig <hch@lst.de> writes:
>
> Christoph> This kills all the cruft needed for supporting anything
> Christoph> other than halfway recent 2.4 and 2.6 kernels. Should make
> Christoph> converting to the pci hotplug APIs much easier.
>
> Looks pretty decent, are you sure the MOD_INC_USE_COUNT isn't needed
> for 2.4.18+ ? (no I haven't checked).
Yes, 2.4 already has the owner field in struct net_device.
prev parent reply other threads:[~2004-01-21 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 14:17 [PATCH] kill ancient compat cruft from acenic Christoph Hellwig
2004-01-21 8:36 ` Jes Sorensen
2004-01-21 9:47 ` Christoph Hellwig [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=20040121094714.GA20425@lst.de \
--to=hch@lst.de \
--cc=jes@wildopensource.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).