From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-wireless <linux-wireless@vger.kernel.org>, netdev@vger.kernel.org
Subject: Re: A generic kernel compatibilty code
Date: Fri, 20 Nov 2009 12:53:51 -0800 [thread overview]
Message-ID: <43e72e890911201253obc466c8k2102e04457c48c92@mail.gmail.com> (raw)
In-Reply-To: <43e72e890911201251t6210ee19n177eaf003a4fffc@mail.gmail.com>
On Fri, Nov 20, 2009 at 12:51 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Fri, Nov 20, 2009 at 12:45 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
>> Everyone and their mother reinvents the wheel when it comes to
>> backporting kernel modules. It a painful job and it seems to me an
>> alternative is possible. If we can write generic compatibilty code for
>> a new routine introduced on the next kernel how about just merging it
>> to the kernel under some generic compat module. This would be
>> completey ignored by everyone using the stable kernel but can be
>> copied by anyone doing backport work.
>>
>> So I'm thinking something as simple as a generic compat/comat.ko with
>> compat-2.6.32.[ch] files.
>
> FWIW, I meant a compat-2.6.32.[ch] and compat-2.6.31.[ch] and so on.
> All these would link to the compat.ko
I supose this could juse be a separate tree with some generic
compat.ko module. That might work better.
Luis
next prev parent reply other threads:[~2009-11-20 20:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 20:45 A generic kernel compatibilty code Luis R. Rodriguez
2009-11-20 20:51 ` Luis R. Rodriguez
2009-11-20 20:53 ` Luis R. Rodriguez [this message]
2009-11-20 21:18 ` John W. Linville
2009-11-20 21:38 ` Luis R. Rodriguez
2009-11-21 2:12 ` Luis R. Rodriguez
2009-11-20 21:00 ` Ben Hutchings
2009-11-20 21:07 ` Luis R. Rodriguez
2009-11-23 13:26 ` Ben Hutchings
2009-11-23 16:20 ` Luis R. Rodriguez
2009-11-20 21:16 ` Mauro Carvalho Chehab
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=43e72e890911201253obc466c8k2102e04457c48c92@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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