From: Linus Walleij <linus.walleij@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>
Cc: Ludovic Desroches <ludovic.desroches@microchip.com>
Subject: Re: [RESEND RFC PATCH 0/2] fixing the gpio ownership
Date: Fri, 19 Jan 2018 22:02:39 +0100 [thread overview]
Message-ID: <CACRpkdaOq=iV5zNG8cXqH_ThF7Aj+GJL0HxA9pBLSvHtd96mrA@mail.gmail.com> (raw)
In-Reply-To: <20180118151211.GW2989@rfolt0960.corp.atmel.com>
On Thu, Jan 18, 2018 at 4:12 PM, Ludovic Desroches
<ludovic.desroches@microchip.com> wrote:
> On Thu, Jan 18, 2018 at 11:16:44AM +0100, Linus Walleij wrote:
>> > It seems
>> > that more and more drivers are converted to use GPIO descriptors so there is
>> > some hope.
>>
>> Yeah I'm doing this when I have time. There is plenty of work...
>> Help appreciated.
>
> I will try to handle the ones related to the platforms I am using.
I'm looking into SPI and regulators for the next kernel cycle, so
those will hopefully get fixed.
Yours,
Linus Walleij
prev parent reply other threads:[~2018-01-19 21:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 16:24 [RESEND RFC PATCH 0/2] fixing the gpio ownership Ludovic Desroches
2018-01-15 16:24 ` [RFC PATCH 1/2] pinctrl: add consumer variant for gpio request Ludovic Desroches
2018-01-15 16:24 ` [RFC PATCH 2/2] gpio: provide a consumer when requesting a gpio Ludovic Desroches
2018-01-18 10:30 ` Linus Walleij
2018-01-18 15:22 ` Ludovic Desroches
2018-01-24 13:07 ` Ludovic Desroches
2018-01-24 15:42 ` Andy Shevchenko
2018-01-26 7:32 ` Ludovic Desroches
2018-01-26 17:13 ` Andy Shevchenko
2018-01-29 13:43 ` Ludovic Desroches
2018-01-18 10:16 ` [RESEND RFC PATCH 0/2] fixing the gpio ownership Linus Walleij
2018-01-18 15:12 ` Ludovic Desroches
2018-01-19 21:02 ` Linus Walleij [this message]
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='CACRpkdaOq=iV5zNG8cXqH_ThF7Aj+GJL0HxA9pBLSvHtd96mrA@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.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).