From: "Michael Büsch" <m@bues.ch>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-mips@linux-mips.org,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Lee Jones" <lee.jones@linaro.org>,
"Matthew Garrett" <matthew.garrett@nebula.com>,
"Samuel Ortiz" <sameo@linux.intel.com>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Tomi Valkeinen" <tomi.valkeinen@ti.com>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"Linux Input" <linux-input@vger.kernel.org>,
"abdoulaye berthe" <berthe.ab@gmail.com>,
"Alexandre Courbot" <gnurou@gmail.com>,
"Bryan Wu" <cooloney@gmail.com>,
"arm@kernel.org" <arm@kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"Mark Brown" <broonie@kernel.org>
Subject: Re: [PATCH 3/3] driver:gpio remove all usage of gpio_remove retval in driver
Date: Tue, 22 Jul 2014 17:17:04 +0200 [thread overview]
Message-ID: <20140722171704.71e34e9e@wiggum> (raw)
In-Reply-To: <CACRpkdasp9bLULT7NJM9nYX58rRSsQKXFddOLz9Ah6kp-j-3=Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 496 bytes --]
On Tue, 22 Jul 2014 17:08:13 +0200
Linus Walleij <linus.walleij@linaro.org> wrote:
> > drivers/ssb/driver_gpio.c | 3 ++-
>
> Michael can you (A) ACK this and
Acked-by: Michael Büsch <m@bues.ch>
> (B) think of moving this driver to drivers/gpio... Patches welcome.
This is not that easy, as it is not a driver on its own, but integral part of ssb.
I don't think it's a good idea to move it out.
I'll accept well tested patches, though.
--
Michael
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2014-07-22 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACRpkda6mzVdaN0cvOxpbsxWyCv2nGyDXOjZg_5aT8u7SSQeUw@mail.gmail.com>
[not found] ` <1405197014-25225-1-git-send-email-berthe.ab@gmail.com>
[not found] ` <1405197014-25225-4-git-send-email-berthe.ab@gmail.com>
2014-07-22 15:08 ` [PATCH 3/3] driver:gpio remove all usage of gpio_remove retval in driver Linus Walleij
2014-07-22 15:11 ` Mark Brown
2014-07-24 8:29 ` Linus Walleij
2014-07-22 15:17 ` Michael Büsch [this message]
2014-07-22 16:01 ` Lee Jones
2014-07-22 17:51 ` Dmitry Torokhov
2014-07-22 19:17 ` Mauro Carvalho Chehab
2014-07-29 11:30 ` Tomi Valkeinen
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=20140722171704.71e34e9e@wiggum \
--to=m@bues.ch \
--cc=alsa-devel@alsa-project.org \
--cc=arm@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=berthe.ab@gmail.com \
--cc=broonie@kernel.org \
--cc=cooloney@gmail.com \
--cc=gnurou@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--cc=sameo@linux.intel.com \
--cc=tomi.valkeinen@ti.com \
--cc=zajec5@gmail.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).