From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/2] MAINTAINERS: regulator: Add Documentation/power/regulator/
Date: Tue, 28 Nov 2017 05:22:02 +0100 [thread overview]
Message-ID: <20171128042201.vwrhaj4jzlah6uy7@latitude> (raw)
In-Reply-To: <20171119050907.5043-1-j.neuschaefer@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
On Sun, Nov 19, 2017 at 06:09:06AM +0100, Jonathan Neuschäfer wrote:
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
Ping.
Should I resend this series with Cc: linux-doc@vger.kernel.org?
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 2811a211632c..a644d41e088c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -14447,6 +14447,7 @@ W: http://www.slimlogic.co.uk/?p=48
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
> S: Supported
> F: Documentation/devicetree/bindings/regulator/
> +F: Documentation/power/regulator/
> F: drivers/regulator/
> F: include/dt-bindings/regulator/
> F: include/linux/regulator/
> --
> 2.11.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-11-28 4:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 5:09 [PATCH 1/2] MAINTAINERS: regulator: Add Documentation/power/regulator/ Jonathan Neuschäfer
2017-11-19 5:09 ` [PATCH 2/2] regulator: Update code examples in documentation Jonathan Neuschäfer
2017-11-28 4:22 ` Jonathan Neuschäfer [this message]
2017-11-28 15:15 ` [PATCH 1/2] MAINTAINERS: regulator: Add Documentation/power/regulator/ Mark Brown
2017-11-28 20:25 ` Jonathan Neuschäfer
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=20171128042201.vwrhaj4jzlah6uy7@latitude \
--to=j.neuschaefer@gmx.net \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@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