All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Denis Turischev <denis@compulab.co.il>
Cc: LKML <linux-kernel@vger.kernel.org>,
	David Brownell <dbrownell@users.sourceforge.net>
Subject: Re: [RESEND] gpio: introduce it8761e_gpio driver for IT8761E Super I/O chip
Date: Tue, 2 Mar 2010 14:40:27 -0800	[thread overview]
Message-ID: <20100302144027.bf6ea1c9.akpm@linux-foundation.org> (raw)
In-Reply-To: <4B8A2F34.3020505@compulab.co.il>

On Sun, 28 Feb 2010 10:54:12 +0200
Denis Turischev <denis@compulab.co.il> wrote:

> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -101,6 +101,12 @@ config GPIO_SCH
>   	  This driver can also be built as a module. If so, the module
>   	  will be called sch-gpio.
> 
> +config GPIO_IT8761E
> +	tristate "IT8761E GPIO support"
> +	depends on GPIOLIB
> +	help
> +	  Say yes here to support GPIO functionality of IT8761E super I/O chip.
> +

The comment said "put expanders in the right section, in alphabetical
order".  It wasn't in alphabetical order ;)

Is this a "Memory mapped GPIO expander"?  Looks like it's IO-mapped,
but there isn't a section in Kconfig for that.  PCI mapped?



  reply	other threads:[~2010-03-02 22:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-28  8:54 [RESEND] gpio: introduce it8761e_gpio driver for IT8761E Super I/O chip Denis Turischev
2010-03-02 22:40 ` Andrew Morton [this message]
2010-03-17 10:09   ` it8761e_gpio: Fixed bug in gpio numbering Denis Turischev
2010-04-28  8:24     ` Denis Turischev
2010-06-30 15:23 ` [PATCH 1/2] gpio: SIO IT8761, Poulsbo SCH are I/O mapped Denis Turischev
2010-06-30 16:17   ` [PATCH 2/2] gpio: introduce f71808e_gpio driver for F71808E Super I/O chip Denis Turischev
2010-06-30 16:37     ` David Brownell
2010-07-01 10:06       ` Denis Turischev

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=20100302144027.bf6ea1c9.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dbrownell@users.sourceforge.net \
    --cc=denis@compulab.co.il \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.