From: Jonathan Cameron <jic23@kernel.org>
To: "Nuno Sá" <nuno.sa@analog.com>
Cc: <linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Michael Hennerich <Michael.Hennerich@analog.com>
Subject: Re: [PATCH 0/2] ad3552r change maintainer and update MAINTAINERS
Date: Sun, 10 Apr 2022 17:59:30 +0100 [thread overview]
Message-ID: <20220410175930.2c80dbc3@jic23-huawei> (raw)
In-Reply-To: <20220404085000.249423-1-nuno.sa@analog.com>
On Mon, 4 Apr 2022 10:49:58 +0200
Nuno Sá <nuno.sa@analog.com> wrote:
> After the bug report in [1], it came to my attention that the maintainer
> for this driver is outdated as Mihail Chindris moved from ADI. As such,
> change the maintainer to myself. On top of this, I then realized there
> was no entry for this driver in MAINTAINERS so add one.
>
> [1]: https://lore.kernel.org/all/20220106103553.GA26440@kili/
>
> Nuno Sá (2):
> dt-bindings: iio: dac: change ad3552r maintainer
> MAINTAINERS: add ad3552r
>
> .../devicetree/bindings/iio/dac/adi,ad3552r.yaml | 2 +-
> MAINTAINERS | 8 ++++++++
> 2 files changed, 9 insertions(+), 1 deletion(-)
>
Series applied to the togreg branch of iio.git an pushed out as testing
so 0-day can poke other stuff I have on that branch.
Thanks,
Jonathan
prev parent reply other threads:[~2022-04-10 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 8:49 [PATCH 0/2] ad3552r change maintainer and update MAINTAINERS Nuno Sá
2022-04-04 8:49 ` [PATCH 1/2] dt-bindings: iio: dac: change ad3552r maintainer Nuno Sá
2022-04-06 18:00 ` Rob Herring
2022-04-04 8:50 ` [PATCH 2/2] MAINTAINERS: add ad3552r Nuno Sá
2022-04-10 16:59 ` Jonathan Cameron [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=20220410175930.2c80dbc3@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh+dt@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).