From: David Woodhouse <dwmw2@infradead.org>
To: mtd@infradead.org
Cc: Erwin Authried <eauth@softsys.co.at>
Subject: Compatibility issues.
Date: Fri, 19 May 2000 12:59:23 +0100 [thread overview]
Message-ID: <21995.958737563@devel2.axiom.internal> (raw)
I would like to have as few occurrences of #if LINUX_VERSION_CODE ... in
the actual source code of the MTD stuff as possible.
The 2.2.15 kernel contains a new file linux/compatmac.h which provides a
handful of useful macros which allow you to write portable code.
This is what I've been using for ensuring compatibility between 2.2 and 2.3
code, and I'd like to provide a similar linux/compatmac.h file to allow us
to compile for 2.0 as well.
I've added linux/mtd/compatmac.h which currently contains the definitions
which are missing from Linus' version - but I'd like my file to become
obsolete as all the required definitions are accepted into the 'official'
version of compatmac.h in both the 2.0 and 2.2 kernels.
So I've removed all references to the sysdep-2.[12].h files, and moved some
of the extra definitions into our own mtd/compatmac.h.
If more are required for fixing the 2.0 build, I'd prefer that they be
added to mtd/compatmac.h, and we can soon delete the sysdep-2.[12].h files
from the repository.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2000-05-19 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-19 11:59 David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-06 20:10 compatibility issues Tomasz Grobelny
2008-04-06 21:57 ` Tomasz Grobelny
2008-04-07 7:46 ` Gerrit Renker
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=21995.958737563@devel2.axiom.internal \
--to=dwmw2@infradead.org \
--cc=eauth@softsys.co.at \
--cc=mtd@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.