From: Alexandre Courbot <gnurou@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: remove self from GPIO maintainers
Date: Wed, 24 May 2017 07:47:00 +0900 [thread overview]
Message-ID: <CAAVeFuJDTrDMRaO1fLXPwp4cZMZy-X2YLsescPHiRe2yUjXBSQ@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdbwSHyHYZrXCGYepCNy+LyK2_N2UtDY87zV26UEY0a0dg@mail.gmail.com>
On Tue, May 23, 2017 at 5:14 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Fri, May 12, 2017 at 7:01 PM, Alexandre Courbot <gnurou@gmail.com> wrote:
>
>> From: Alexandre Courbot <gnurou@gmail.com>
>>
>> I have not been able to dedicate time to the GPIO subsystem since quite
>> some time, and I don't see the situation improving in the near future.
>> Update the maintainers list to reflect this unfortunate fact.
>>
>> Signed-off-by: Alexandre Courbot <gnurou@gmail.com>
>
> Sad to see you go :(
Me too, honestly. :/
> However I see the work you are doing on Noveau and such that is
> also extremely important.
Sadly my work on Nouveau is also in the past. I am more headed towards V4L now.
> Do you have a TODO with e.g. gpiod conversions etc that you
> have planned but never go to you could submit? I'd be happy to
> carry that in Documentation/gpio/TODO or so.
Nothing in particular, last time I have checked it seemed that at
least new drivers were sticking to gpiod, which is nice to see!
Thanks for everything, and probably see you again!
Alex.
prev parent reply other threads:[~2017-05-23 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 17:01 [PATCH] MAINTAINERS: remove self from GPIO maintainers Alexandre Courbot
2017-05-12 19:00 ` Andy Shevchenko
2017-05-15 17:59 ` Alexandre Courbot
2017-05-23 8:14 ` Linus Walleij
2017-05-23 22:47 ` Alexandre Courbot [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=CAAVeFuJDTrDMRaO1fLXPwp4cZMZy-X2YLsescPHiRe2yUjXBSQ@mail.gmail.com \
--to=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--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 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).