From: Gregory Haskins <gregory.haskins@gmail.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: NET: Questions about supporting older kernel's with kmods
Date: Thu, 19 Nov 2009 09:59:18 -0500 [thread overview]
Message-ID: <4B055D46.6060407@gmail.com> (raw)
In-Reply-To: <1258642393.2837.5.camel@achroite.uk.solarflarecom.com>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
Ben Hutchings wrote:
> On Thu, 2009-11-19 at 09:21 -0500, Gregory Haskins wrote:
[...]
>
>> or should I simply look at the kernel version?
>
> That works up to a point, but the 'enterprise' distros backport a lot to
> earlier kernel versions which can make version tests invalid.
Good point
>
> Some out-of-tree/backported drivers use autoconf-style tests, but there
> is no standard way of doing this.
>
Yeah, this might be the only sane way. It turns out that my ETHTOOL
issue was trivial. I was missing "#include <linux/ethtool.h>" which
worked in upstream, but not in older kernels. So that issue is resolved.
Now I just need to figure out netdev_ops. Perhaps I will just patch the
netdev_ops out when building a kmod, since its just
a different way to describe the same thing, and the resulting driver
will perform the same.
> [...]
>> Q2) Is it considered "bad form" to include such compile-time directives
>> in the version of the code going upstream?
> [...]
>
> Yes. Don't do that.
Ok.
Thanks Ben,
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 267 bytes --]
prev parent reply other threads:[~2009-11-19 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 14:21 NET: Questions about supporting older kernel's with kmods Gregory Haskins
2009-11-19 14:53 ` Ben Hutchings
2009-11-19 14:59 ` Gregory Haskins [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=4B055D46.6060407@gmail.com \
--to=gregory.haskins@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).