From: Felix Fietkau <nbd@openwrt.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: John W Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: [RFC] rtlwifi: Fix build failures due to raw port access
Date: Thu, 04 Aug 2011 21:03:26 +0200 [thread overview]
Message-ID: <4E3AECFE.6030900@openwrt.org> (raw)
In-Reply-To: <4e3aea9b.T53ak5bZ1r+a9cJM%Larry.Finger@lwfinger.net>
On 2011-08-04 8:53 PM, Larry Finger wrote:
> When rtlwifi is built for the sh4 architecture, build errors of the following
> type occur. As these raw port accesses are specific to the X86 architecture,
> their usage is restricted and dummy routines are substituted for all other
> platforms.
By the way, even on x86 I'd recommend getting rid of this code. It seems
that ASPM handling is mostly sorted out in the kernel, so that kind of
hacks should no longer be necessary.
- Felix
prev parent reply other threads:[~2011-08-04 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 18:53 [RFC] rtlwifi: Fix build failures due to raw port access Larry Finger
2011-08-04 19:03 ` Felix Fietkau [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=4E3AECFE.6030900@openwrt.org \
--to=nbd@openwrt.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).