All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: linux-iio@vger.kernel.org,
	Marek Vasut <marek.vasut+renesas@gmail.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Joe Perches <joe@perches.com>,
	Jonathan Cameron <jic23@kernel.org>,
	Simon Horman <horms+renesas@verge.net.au>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] iio: adc: Fix Renesas GyroADC MAINTAINERS entry
Date: Mon, 1 Oct 2018 14:17:40 +0200	[thread overview]
Message-ID: <20181001121739.GB4134@kunai> (raw)
In-Reply-To: <bc65ecfa-5135-5224-bdeb-938b3025c30c@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 708 bytes --]

On Mon, Oct 01, 2018 at 01:58:26PM +0200, Marek Vasut wrote:
> On 10/01/2018 01:55 PM, Wolfram Sang wrote:
> > On Mon, Oct 01, 2018 at 12:58:04PM +0200, Marek Vasut wrote:
> >> Fix the F: entry in MAINTAINERS file, point it to the correct file.
> > 
> > Right...
> > 
> >> @@ -12471,7 +12471,7 @@ RENESAS R-CAR GYROADC DRIVER
> >>  M:	Marek Vasut <marek.vasut@gmail.com>
> >>  L:	linux-iio@vger.kernel.org
> >>  S:	Supported
> >> -F:	drivers/iio/adc/rcar_gyro_adc.c
> >> +F:	drivers/iio/adc/rcar-gyroadc.c
> > 
> > Add the bindings, too?
> > 
> > Documentation/devicetree/bindings/iio/adc/renesas,gyroadc.txt
> > 
> Separate patch or V2 ?

I'd say V2, but I am not the IIO maintainer.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-10-01 18:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01 10:58 [PATCH] iio: adc: Fix Renesas GyroADC MAINTAINERS entry Marek Vasut
2018-10-01 11:55 ` Wolfram Sang
2018-10-01 11:58   ` Marek Vasut
2018-10-01 12:17     ` Wolfram Sang [this message]
2018-10-01 12:20       ` Jonathan Cameron
2018-10-02  1:00         ` Marek Vasut

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=20181001121739.GB4134@kunai \
    --to=wsa@the-dreams.de \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@verge.net.au \
    --cc=jic23@kernel.org \
    --cc=joe@perches.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=marek.vasut+renesas@gmail.com \
    --cc=marek.vasut@gmail.com \
    /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.