From: Marek Vasut <marek.vasut@gmail.com>
To: Joe Perches <joe@perches.com>, linux-kernel@vger.kernel.org
Cc: linux-iio@vger.kernel.org
Subject: Re: Bad MAINTAINERS pattern in section 'RENESAS R-CAR GYROADC DRIVER'
Date: Mon, 1 Oct 2018 12:58:32 +0200 [thread overview]
Message-ID: <6b5b6ff4-1575-706e-defe-03fe4223c155@gmail.com> (raw)
In-Reply-To: <20180928220152.31151-1-joe@perches.com>
On 09/29/2018 12:01 AM, Joe Perches wrote:
> Please fix this defect appropriately.
>
> linux-next MAINTAINERS section:
>
> 12496 RENESAS R-CAR GYROADC DRIVER
> 12497 M: Marek Vasut <marek.vasut@gmail.com>
> 12498 L: linux-iio@vger.kernel.org
> 12499 S: Supported
> --> 12500 F: drivers/iio/adc/rcar_gyro_adc.c
>
> Commit that introduced this:
>
> commit 059c53b3232960cfd38cc46de0a7bedd642021f5
> Author: Marek Vasut <marek.vasut+renesas@gmail.com>
> Date: Sat Jan 28 00:08:37 2017 +0100
>
> iio: adc: Add Renesas GyroADC driver
>
> Add IIO driver for the Renesas RCar GyroADC block. This block is a
> simple 4/8-channel ADC which samples 12/15/24 bits of data every
> cycle from all channels.
>
> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
> Cc: Simon Horman <horms+renesas@verge.net.au>
> Cc: Jonathan Cameron <jic23@kernel.org>
> Cc: linux-renesas-soc@vger.kernel.org
> Cc: Wolfram Sang <wsa@the-dreams.de>
> Signed-off-by: Jonathan Cameron <jic23@kernel.org>
>
> MAINTAINERS | 6 +
> drivers/iio/adc/Kconfig | 13 +
> drivers/iio/adc/Makefile | 1 +
> drivers/iio/adc/rcar-gyroadc.c | 631 +++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 651 insertions(+)
>
> No commit with drivers/iio/adc/rcar_gyro_adc.c found
>
Fixed, thanks for the heads up.
--
Best regards,
Marek Vasut
parent reply other threads:[~2018-10-01 17:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180928220152.31151-1-joe@perches.com>]
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=6b5b6ff4-1575-706e-defe-03fe4223c155@gmail.com \
--to=marek.vasut@gmail.com \
--cc=joe@perches.com \
--cc=linux-iio@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).