From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: linux-iio <linux-iio@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ekigwana@gmail.com, Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v3 3/3] MAINTAINERS: add entry for ADF4360 PLL driver
Date: Mon, 3 Feb 2020 12:26:31 +0200 [thread overview]
Message-ID: <CAHp75VcHU=PBzxFoLTtVMBkdB8Z0BcRQ2bq8D50YoRNPisxfcQ@mail.gmail.com> (raw)
In-Reply-To: <20200128111302.24359-3-alexandru.ardelean@analog.com>
On Tue, Jan 28, 2020 at 1:13 PM Alexandru Ardelean
<alexandru.ardelean@analog.com> wrote:
>
> From: Edward Kigwana <ekigwana@gmail.com>
>
> Add entry in the MAINTAINERS file for the ADF4360 PLL driver.
> +ADF4360 PLL DRIVER
> +M: Edward Kigwana <ekigwana@gmail.com>
> +W: http://ez.analog.com/community/linux-device-drivers
> +L: linux-iio@vger.kernel.org
> +S: Maintained
> +F: Documentation/devicetree/bindings/iio/frequency/adi,adf4360.yaml
> +F: drivers/iio/frequency/adf4360.c
Had you run parse-maintainers.pl afterwards to see if everything is okay?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-02-03 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 11:13 [PATCH v3 1/3] iio: frequency: adf4360: Add support for ADF4360 PLLs Alexandru Ardelean
2020-01-28 11:13 ` [PATCH v3 2/3] dt-bindings: iio: frequency: Add docs for ADF4360 PLL Alexandru Ardelean
2020-02-02 14:47 ` Jonathan Cameron
2020-02-05 18:24 ` Rob Herring
2020-01-28 11:13 ` [PATCH v3 3/3] MAINTAINERS: add entry for ADF4360 PLL driver Alexandru Ardelean
2020-02-03 10:26 ` Andy Shevchenko [this message]
2020-02-02 14:45 ` [PATCH v3 1/3] iio: frequency: adf4360: Add support for ADF4360 PLLs Jonathan Cameron
2020-02-03 11:18 ` Ardelean, Alexandru
2020-02-03 11:27 ` Jonathan Cameron
2020-02-03 14:10 ` Andy Shevchenko
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='CAHp75VcHU=PBzxFoLTtVMBkdB8Z0BcRQ2bq8D50YoRNPisxfcQ@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=alexandru.ardelean@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=ekigwana@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.