From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: "long17.cool@163.com" <long17.cool@163.com>
Cc: "a.zummo" <a.zummo@towertech.it>,
"mark.rutland" <mark.rutland@arm.com>,
linux-rtc <linux-rtc@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Re: [PATCH 3/4] dt-bindings: rtc: sd3078: add device tree documentation
Date: Mon, 12 Nov 2018 18:40:40 +0100 [thread overview]
Message-ID: <20181112174040.GG29768@piout.net> (raw)
In-Reply-To: <201811130055486298716@163.com>
On 13/11/2018 00:55:49+0800, long17.cool@163.com wrote:
> hello：
> The patch of 4/4 is not used for this modules, this is my problem.
>
> I have a question :
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -16130,6 +16130,7 @@ M: Zoro Li <long17.cool@163.com>
> > L: linux-rtc@vger.kernel.org
> > S: Maintained
> > F: drivers/rtc/rtc-sd3078.c
> > +F: Documentation/devicetree/bindings/rtc/rtc-sd3078.txt
> >
>
> There is no need to list this file here if it is only done to silence checkpatch.
> What does it mean?
>
> I found that if I didn't add that statement, when I checkpatch,
> I would get the following warning.
> WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
> #16:
> new file mode 100644
> Can I ignore this warning?
>
Yes, you can.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-11-12 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 5:45 [PATCH 1/4] dt-bindings: define vendor prefix for whwave, Inc zoro
2018-11-12 5:45 ` [PATCH 2/4] rtc: sd3078: new driver zoro
2018-11-12 15:46 ` Alexandre Belloni
2018-11-12 5:45 ` [PATCH 3/4] dt-bindings: rtc: sd3078: add device tree documentation zoro
2018-11-12 15:49 ` Alexandre Belloni
[not found] ` <201811130055486298716@163.com>
2018-11-12 17:40 ` Alexandre Belloni [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=20181112174040.GG29768@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=long17.cool@163.com \
--cc=mark.rutland@arm.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.