From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Wolfram Sang <wsa@the-dreams.de>, Denis Efremov <efremov@linux.com>
Cc: linux-kernel@vger.kernel.org, joe@perches.com,
Maxime Ripard <maxime.ripard@bootlin.com>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: i2c mv64xxx: Update documentation path
Date: Fri, 30 Aug 2019 10:31:03 +0200 [thread overview]
Message-ID: <87a7brxdfc.fsf@FE-laptop> (raw)
In-Reply-To: <20190829200055.GJ3740@ninjato>
Wolfram Sang <wsa@the-dreams.de> writes:
> On Tue, Aug 13, 2019 at 09:09:13AM +0300, Denis Efremov wrote:
>> Update MAINTAINERS record to reflect the file move
>> from i2c-mv64xxx.txt to marvell,mv64xxx-i2c.yaml.
>>
>> Cc: Maxime Ripard <maxime.ripard@bootlin.com>
>> Cc: Gregory CLEMENT <gregory.clement@bootlin.com>
>> Cc: linux-i2c@vger.kernel.org
>> Fixes: f8bbde72ef44 ("dt-bindings: i2c: mv64xxx: Add YAML schemas")
>> Signed-off-by: Denis Efremov <efremov@linux.com>
>
> Looks OK to me, Gregory or Maxime?
Acked-by: Gregory CLEMENT <gregory.clement@bootlin.com>
Thanks,
Gregory
>
>> ---
>> MAINTAINERS | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 87ac0378186c..590dcebe627f 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -7505,7 +7505,7 @@ I2C MV64XXX MARVELL AND ALLWINNER DRIVER
>> M: Gregory CLEMENT <gregory.clement@bootlin.com>
>> L: linux-i2c@vger.kernel.org
>> S: Maintained
>> -F: Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt
>> +F: Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml
>> F: drivers/i2c/busses/i2c-mv64xxx.c
>>
>> I2C OVER PARALLEL PORT
>> --
>> 2.21.0
>>
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2019-08-30 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7cd8d12f59bcacd18a78f599b46dac555f7f16c0.camel@perches.com>
2019-08-13 6:09 ` [PATCH] MAINTAINERS: i2c mv64xxx: Update documentation path Denis Efremov
2019-08-29 20:00 ` Wolfram Sang
2019-08-30 8:28 ` Maxime Ripard
2019-08-30 8:31 ` Gregory CLEMENT [this message]
2019-08-30 12:38 ` Wolfram Sang
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=87a7brxdfc.fsf@FE-laptop \
--to=gregory.clement@bootlin.com \
--cc=efremov@linux.com \
--cc=joe@perches.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=wsa@the-dreams.de \
/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).