From: Michael Buesch <mb@bu3sch.de>
To: Greg KH <greg@kroah.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
Paul Hickey <paul@christianpatriot.us>,
stable@kernel.org, Kyle McMartin <kyle@mcmartin.ca>,
linux-wireless@vger.kernel.org,
Luis Rodriguez <Luis.Rodriguez@atheros.com>
Subject: Re: [stable] Failed Build of modules for 2.6.27.9-159
Date: Tue, 20 Jan 2009 21:15:21 +0100 [thread overview]
Message-ID: <200901202115.22231.mb@bu3sch.de> (raw)
In-Reply-To: <20090120200515.GA5077@kroah.com>
On Tuesday 20 January 2009 21:05:15 Greg KH wrote:
> > I am =FCber-surprised to hear that FC10 2.6.27 kernels have added
> > pci_ioremap_bar() in their kernel header include/linux/pci.h. I
> > have verified this by checking:
> >=20
> > http://download.fedora.redhat.com/pub/fedora/linux/updates/10/x86_6=
4/kernel-devel-2.6.27.9-159.fc10.x86_64.rpm
> >=20
> > I have checked upstrea 2.6.27.9 and even 2.6.27.12 and they do not =
have this. This breaks
> > compatibility projects like compat-wireless :(
>=20
> compatibility projects should be checking for the absense or presence=
of
> specific functions, not triggering off of kernel release numbers :)
Yeah, well. But it's hard to do, if you can't do it in the preprocessor=
=2E
So you can really only check for macros, not functions.
--=20
Greetings, Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-01-20 20:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 23:04 Failed Build of modules for 2.6.27.9-159 Paul Hickey
2009-01-19 19:11 ` Luis R. Rodriguez
[not found] ` <1232404986.3641.2.camel@localhost.localdomain>
[not found] ` <20090120000336.GB4018@tesla>
[not found] ` <1232433738.3696.3.camel@localhost.localdomain>
2009-01-20 19:42 ` Luis R. Rodriguez
2009-01-20 20:05 ` [stable] " Greg KH
2009-01-20 20:13 ` Luis R. Rodriguez
2009-01-20 20:16 ` Greg KH
[not found] ` <20090120211630.GJ19581@tesla>
2009-01-20 22:08 ` Kyle McMartin
2009-01-20 22:37 ` Greg KH
2009-01-20 22:55 ` Luis R. Rodriguez
2009-01-20 23:23 ` Kyle McMartin
2009-01-21 0:07 ` Luis R. Rodriguez
2009-01-21 0:12 ` Kyle McMartin
2009-01-21 0:20 ` Luis R. Rodriguez
2009-01-20 20:15 ` Michael Buesch [this message]
2009-01-20 21:12 ` Kyle McMartin
2009-01-20 21:21 ` Luis R. Rodriguez
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=200901202115.22231.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Luis.Rodriguez@atheros.com \
--cc=greg@kroah.com \
--cc=kyle@mcmartin.ca \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=paul@christianpatriot.us \
--cc=stable@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).