From: alexander.sverdlin@gmail.com (Alexander Sverdlin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/5] iio: ADC driver for EP93xx SoC
Date: Mon, 22 May 2017 07:41:48 +0200 [thread overview]
Message-ID: <d0adb2f7-8e46-bfa9-b256-daf7f1a3544f@gmail.com> (raw)
In-Reply-To: <5921F894.90809@gmail.com>
Hello Ryan!
On 21/05/17 22:29, Ryan Mallon wrote:
>> How do you want to handle taking this series forward.
>> Clearly we have a few arch specific bits and then the driver which
>> is dependent on some of them.
> I no longer maintain an ep93xx tree because the architecture gets very
> few patches now. Patches should go via the arm-soc tree, which is
> maintained by (I believe) Arnd and Olaf.
This probably should be reflected in MAINTAINERS file?
Do you want to drop EP93xx maintenance?
In this case I can volunteer myself as a maintainer for the platform.
--
Best regards,
Alexander.
next prev parent reply other threads:[~2017-05-22 5:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 17:13 [PATCH v4 0/5] iio: ADC driver for EP93xx SoC Alexander Sverdlin
2017-05-17 17:13 ` [PATCH v4 1/5] clk: ep93xx: Implement clk_get_parent() Alexander Sverdlin
2017-05-17 17:13 ` [PATCH v4 2/5] clk: ep93xx: Add ADC clock Alexander Sverdlin
2017-05-17 17:13 ` [PATCH v4 3/5] ep93xx: Add ADC platform device support to core Alexander Sverdlin
2017-05-17 17:13 ` [PATCH v4 4/5] edb93xx: Add ADC platform device Alexander Sverdlin
2017-05-17 17:13 ` [PATCH v4 5/5] iio: adc: New driver for Cirrus Logic EP93xx ADC Alexander Sverdlin
2017-05-21 14:03 ` [PATCH v4 0/5] iio: ADC driver for EP93xx SoC Jonathan Cameron
2017-05-21 20:29 ` Ryan Mallon
2017-05-22 5:41 ` Alexander Sverdlin [this message]
2017-05-22 6:51 ` Ryan Mallon
2017-06-03 9:14 ` Jonathan Cameron
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=d0adb2f7-8e46-bfa9-b256-daf7f1a3544f@gmail.com \
--to=alexander.sverdlin@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).