From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] ia64: Hook up gpiolib support
Date: Wed, 01 Jun 2011 19:34:53 +0000 [thread overview]
Message-ID: <20110601193453.GB12949@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1306921697-31045-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Wed, Jun 01, 2011 at 01:33:34PM -0600, Grant Likely wrote:
> On Wed, Jun 1, 2011 at 1:31 PM, Mark Brown
> > On Wed, Jun 01, 2011 at 12:12:37PM -0700, Luck, Tony wrote:
> >> + select ARCH_WANT_OPTINAL_GPIOLIB
> >> "OPTINAL"? ... presumably "OPTIONAL" (or "OPTIMAL" :-)
> > Should be OPTINAL, yes.
> Same typo again? :-)
Bah, humbg. :P
next prev parent reply other threads:[~2011-06-01 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 9:48 [PATCH] ia64: Hook up gpiolib support Mark Brown
2011-06-01 19:12 ` Luck, Tony
2011-06-01 19:31 ` Mark Brown
2011-06-01 19:33 ` Grant Likely
2011-06-01 19:34 ` Mark Brown [this message]
2011-06-01 20:15 ` Grant Likely
2011-06-01 20:25 ` Mark Brown
2011-06-01 21:07 ` Tony Luck
2011-06-02 10:07 ` Mark Brown
2011-06-02 17:00 ` Luck, Tony
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=20110601193453.GB12949@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-ia64@vger.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