From: Stephen Rothwell <sfr@canb.auug.org.au>
To: abdoulaye berthe <berthe.ab@gmail.com>
Cc: devel@driverdev.osuosl.org, Alexandre Courbot <gnurou@gmail.com>,
spear-devel@list.st.com, m@bues.ch, linux-mips@linux-mips.org,
linux-sh@vger.kernel.org, netdev@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
patches@opensource.wolfsonmicro.com,
linux-wireless@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-samsungsoc@vger.kernel.org,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
David Daney <ddaney.cavm@gmail.com>,
linux-input@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-leds@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH] gpio: removes all usage of gpiochip_remove retval
Date: Fri, 30 May 2014 09:40:25 +1000 [thread overview]
Message-ID: <20140530094025.3b78301e@canb.auug.org.au> (raw)
In-Reply-To: <CABprBybQ-Jyk95zCqnoWjjyzhNyHVbsbEhb=vA5d=ZYp95_bFA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
Hi abdoulaye,
On Fri, 30 May 2014 01:16:22 +0200 abdoulaye berthe <berthe.ab@gmail.com> wrote:
>
> The aim of this patch is to make gpiochip_remove() behavior consistent,
> especially when issuing a remove request while the chipio chip is
> still requested. A patch has been submitted to change the return value of
> gpiochip_remove() from int to void. This one updates users of the return
> value:
Then you need to keep these two patch in a series with this one first
to make sure that the other patch is not applied without this one.
And you should add the above explanation to the changelog for this
patch.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-29 23:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 21:54 [PATCH] gpio: removes all usage of gpiochip_remove retval abdoulaye berthe
2014-05-29 22:14 ` David Daney
2014-05-29 23:16 ` abdoulaye berthe
2014-05-29 23:40 ` Stephen Rothwell [this message]
2014-05-30 11:30 ` [PATCH 1/2] " abdoulaye berthe
2014-05-30 11:30 ` [PATCH 2/2] gpio: gpiolib: set gpiochip_remove retval to void abdoulaye berthe
2014-05-30 11:39 ` Geert Uytterhoeven
2014-05-30 15:48 ` Ralf Baechle
2014-05-30 17:33 ` David Daney
2014-05-30 18:16 ` Lars-Peter Clausen
2014-05-30 23:29 ` Greg KH
2014-05-31 7:35 ` Lars-Peter Clausen
2014-05-31 12:19 ` Dan Carpenter
2014-06-08 23:18 ` Ben Dooks
2014-06-09 11:29 ` Lars-Peter Clausen
2014-05-29 23:25 ` [PATCH] gpio: removes all usage of gpiochip_remove retval Greg KH
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=20140530094025.3b78301e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=berthe.ab@gmail.com \
--cc=ddaney.cavm@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-samsungsoc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m@bues.ch \
--cc=netdev@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=spear-devel@list.st.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).