From: jrnieder@gmail.com (Jonathan Nieder)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: ixp4xx: fix compilation, add gpiolib support
Date: Tue, 24 Apr 2012 01:10:27 -0500 [thread overview]
Message-ID: <20120424061027.GA23859@burratino> (raw)
In-Reply-To: <20120412052518.GA3260@netboy.at.omicron.at>
Richard Cochran wrote:
> On Wed, Feb 08, 2012 at 08:24:28PM +0100, Marc Kleine-Budde wrote:
>> From: Imre Kaloz <kaloz@openwrt.org>
>>
>> The problem was introduced with commit:
>> "eb9ae7f gpio: fix build error in include/asm-generic/gpio.h"
>>
>> This patch adds gpiolib support for the IXP4xx platform, which fixes the
>> compilation of several ixp4xx platforms, e.g.:
>
> Sorry to nag, but is someone going to take this patch?
It looks like Russell's question[*] was never answered:
| Does anything on ixp4xx require fast access to on-chip GPIOs? If not,
| it would be much better to get rid of this and just use the standard
| wrapping, which can be done by changing this entire file to be just a
| single line:
Hope that helps,
Jonathan
[*] http://thread.gmane.org/gmane.linux.kernel/1250585/focus=1250908
next prev parent reply other threads:[~2012-04-24 6:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 19:24 [PATCH 0/2] ARM: ixp4xx: fix compilation and oops Marc Kleine-Budde
2012-02-08 19:24 ` [PATCH 1/2] ARM: ixp4xx: fix compilation, add gpiolib support Marc Kleine-Budde
2012-02-09 9:04 ` Mikael Pettersson
2012-02-09 9:08 ` Marc Kleine-Budde
2012-02-09 10:57 ` Arnaud Patard (Rtp)
2012-02-09 13:37 ` Marc Kleine-Budde
2012-02-09 9:11 ` Russell King - ARM Linux
2012-02-09 13:40 ` Marc Kleine-Budde
2012-02-09 14:33 ` Russell King - ARM Linux
2012-04-12 5:25 ` Richard Cochran
2012-04-24 6:10 ` Jonathan Nieder [this message]
2012-02-08 19:24 ` [PATCH 2/2] mtd: ixp4xx: oops in ixp4xx_flash_probe Marc Kleine-Budde
2012-02-09 12:11 ` Artem Bityutskiy
2012-02-09 13:15 ` Marc Kleine-Budde
2012-04-07 15:18 ` [PATCH 0/2] ARM: ixp4xx: fix compilation and oops Richard Cochran
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=20120424061027.GA23859@burratino \
--to=jrnieder@gmail.com \
--cc=linux-arm-kernel@lists.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 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).