From: German Rivera <German.Rivera@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: Kim Phillips <kim.phillips@freescale.com>,
"<gregkh@linuxfoundation.org>" <gregkh@linuxfoundation.org>,
"<arnd@arndb.de>" <arnd@arndb.de>,
"<linux-kernel@vger.kernel.org>" <linux-kernel@vger.kernel.org>,
"<stuart.yoder@freescale.com>" <stuart.yoder@freescale.com>,
"<scottwood@freescale.com>" <scottwood@freescale.com>,
"<linuxppc-release@linux.freescale.net>"
<linuxppc-release@linux.freescale.net>
Subject: Re: [PATCH 0/4] drivers/bus: Freescale Management Complex bus driver patch series
Date: Thu, 18 Sep 2014 19:31:03 -0500 [thread overview]
Message-ID: <541B7947.2070901@freescale.com> (raw)
In-Reply-To: <B83A7221-35BF-4E20-8AC4-333A2C0A39B7@suse.de>
On 09/18/2014 07:58 AM, Alexander Graf wrote:
>>
>>> checkpatch:
>>>
>>> WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
>>>
>>> WARNING: DT compatible string "fsl,qoriq-mc" appears un-documented -- check ./Documentation/devicetree/bindings/
>>> #690: FILE: drivers/bus/fsl-mc/fsl_mc_bus.c:528:
>>> + {.compatible = "fsl,qoriq-mc",},
>>>
>>> For the former warning, I'd suggest moving patch 4/4's contents up
>>> in the series.
>> I tried moving 4/4 to be 1/4 but still get the the same warning from checkpatch. So, this suggestion does not work. Besides, I took a look
>> at other commits that update the MAINTAINERS such as
>> 563da3a90364fc29cd09bed034162592e591747a, and that commit comes after the commits that added the new files.
>
> The alternative would be to add MAINTAINERS entries for the files you add in the patch that adds the files.
>
I tried this but still get the checpatch warning:
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
Still, I will add MAINTAINERS entries in each patch that adds files,
instead of having a separate patch just for that.
>
> Alex
>
prev parent reply other threads:[~2014-09-19 0:45 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 17:34 [PATCH 0/4] drivers/bus: Freescale Management Complex bus driver patch series J. German Rivera
2014-09-11 17:34 ` [PATCH 1/4] drivers/bus: Added Freescale Management Complex APIs J. German Rivera
2014-09-11 18:45 ` Joe Perches
2014-09-17 16:35 ` German Rivera
2014-09-15 23:44 ` Kim Phillips
2014-09-16 4:31 ` Scott Wood
2014-09-16 19:28 ` Kim Phillips
2014-09-16 19:58 ` Scott Wood
2014-09-18 4:17 ` German Rivera
2014-09-18 13:14 ` Alexander Graf
2014-09-18 20:22 ` Kim Phillips
2014-09-18 23:03 ` Scott Wood
2014-09-18 23:13 ` Stuart Yoder
2014-09-18 23:29 ` Scott Wood
2014-09-18 23:46 ` Stuart Yoder
2014-09-19 3:05 ` German Rivera
2014-09-19 17:19 ` Kim Phillips
2014-09-19 19:06 ` Stuart Yoder
2014-09-19 20:24 ` Kim Phillips
2014-09-19 20:32 ` Alexander Graf
2014-09-19 20:41 ` Scott Wood
2014-09-19 21:46 ` Alexander Graf
2014-09-20 15:36 ` Stuart Yoder
2014-09-19 21:37 ` Stuart Yoder
2014-09-19 21:30 ` Stuart Yoder
2014-09-19 0:18 ` Stuart Yoder
2014-09-19 2:34 ` German Rivera
2014-09-19 18:25 ` Stuart Yoder
2014-09-19 20:58 ` Kim Phillips
2014-09-22 14:42 ` Stuart Yoder
2014-09-22 14:57 ` <gregkh@linuxfoundation.org>
2014-09-22 15:01 ` Stuart Yoder
2014-09-18 23:39 ` Stuart Yoder
2014-09-18 23:53 ` Scott Wood
2014-09-11 17:34 ` [PATCH 2/4] drivers/bus: Freescale Management Complex (fsl-mc) bus driver J. German Rivera
2014-09-11 18:49 ` Joe Perches
2014-09-17 23:50 ` German Rivera
2014-09-11 17:34 ` [PATCH 3/4] drivers/bus: Device driver for FSL-MC DPRC devices J. German Rivera
2014-09-11 17:34 ` [PATCH 4/4] Update MAINTAINERS file J. German Rivera
2014-09-15 23:44 ` [PATCH 0/4] drivers/bus: Freescale Management Complex bus driver patch series Kim Phillips
2014-09-18 0:20 ` German Rivera
2014-09-18 12:58 ` Alexander Graf
2014-09-19 0:31 ` German Rivera [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=541B7947.2070901@freescale.com \
--to=german.rivera@freescale.com \
--cc=agraf@suse.de \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=kim.phillips@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-release@linux.freescale.net \
--cc=scottwood@freescale.com \
--cc=stuart.yoder@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox