All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, kernel@pengutronix.de,
	Gavin Schenk <g.schenk@eckelmann.de>
Subject: Re: [PATCH v1 4/5] gpio: new driver to work with a 8x12 siox
Date: Mon, 18 Dec 2017 16:09:10 +0100	[thread overview]
Message-ID: <20171218150910.GC25024@kroah.com> (raw)
In-Reply-To: <20171207093008.20688-5-u.kleine-koenig@pengutronix.de>

On Thu, Dec 07, 2017 at 10:30:07AM +0100, Uwe Kleine-König wrote:
> This driver controls a SIOX device that provides 20 I/O lines. The first
> twelve are fixed inputs, the remaining eight are outputs.
> 
> Acked-by: Gavin Schenk <g.schenk@eckelmann.de>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
>  drivers/gpio/Kconfig     |   8 ++
>  drivers/gpio/Makefile    |   1 +
>  drivers/gpio/gpio-siox.c | 293 +++++++++++++++++++++++++++++++++++++++++++++++
>  3 files changed, 302 insertions(+)
>  create mode 100644 drivers/gpio/gpio-siox.c

I can't take this through my tree, but if the gpio maintainer acks it, I
can :)

thanks,

greg k-h

  reply	other threads:[~2017-12-18 15:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07  9:30 [PATCH v1 0/5] siox: add support for new bus type Uwe Kleine-König
2017-12-07  9:30 ` [PATCH v1 1/5] siox: new driver framework for eckelmann SIOX Uwe Kleine-König
2017-12-18 15:06   ` Greg Kroah-Hartman
2017-12-18 15:08   ` Greg Kroah-Hartman
2017-12-18 15:44     ` Uwe Kleine-König
2017-12-07  9:30 ` [PATCH v1 2/5] siox: add support for tracing Uwe Kleine-König
2017-12-07  9:30 ` [PATCH v1 3/5] siox: add gpio bus driver Uwe Kleine-König
2017-12-07  9:30 ` [PATCH v1 4/5] gpio: new driver to work with a 8x12 siox Uwe Kleine-König
2017-12-18 15:09   ` Greg Kroah-Hartman [this message]
2017-12-18 15:40     ` Uwe Kleine-König
2017-12-07  9:30 ` [PATCH v1 5/5] MAINTAINERS: Add entry for SIOX Uwe Kleine-König

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=20171218150910.GC25024@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=g.schenk@eckelmann.de \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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.