From: Greg KH <greg@kroah.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
Paul Hickey <paul@christianpatriot.us>,
"stable@kernel.org" <stable@kernel.org>,
Kyle McMartin <kyle@mcmartin.ca>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [stable] Failed Build of modules for 2.6.27.9-159
Date: Tue, 20 Jan 2009 12:16:13 -0800 [thread overview]
Message-ID: <20090120201613.GA5313@kroah.com> (raw)
In-Reply-To: <20090120201316.GG19581@tesla>
On Tue, Jan 20, 2009 at 12:13:16PM -0800, Luis R. Rodriguez wrote:
> On Tue, Jan 20, 2009 at 12:05:15PM -0800, Greg KH wrote:
> > On Tue, Jan 20, 2009 at 11:42:43AM -0800, Luis R. Rodriguez wrote:
> > > On Mon, Jan 19, 2009 at 10:42:18PM -0800, Paul Hickey wrote:
> > > > Hi Luis,
> > > >
> > > > 2.6.27.9-159.fc10.x86_64 is the kernel. I burned the distro rig=
ht from
> > > > Fedora.
> > >
> > > 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:
> > >
> > > http://download.fedora.redhat.com/pub/fedora/linux/updates/10/x86=
_64/kernel-devel-2.6.27.9-159.fc10.x86_64.rpm
> > >
> > > I have checked upstrea 2.6.27.9 and even 2.6.27.12 and they do no=
t have this. This breaks
> > > compatibility projects like compat-wireless :(
> >=20
> > compatibility projects should be checking for the absense or presen=
ce of
> > specific functions, not triggering off of kernel release numbers :)
>=20
> How can I do that? #ifdef no worky on static inlines, for example.
You can automatically test if the feature is there, right? If so, then
set your own #define for your compatiblity wrappers.
> BTW are you saying the above practice of adding new stuff to headers
> is OK too? I wish it wasn't...
Sure it's ok, distros can do whatever they want in their kernels, are
you telling them that they are now not allowed to do that? :)
thanks,
greg k-h
--
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:18 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 [this message]
[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
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=20090120201613.GA5313@kroah.com \
--to=greg@kroah.com \
--cc=Luis.Rodriguez@Atheros.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).