From: Tejun Heo <tj@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: [PATCH 24/54] MAINTAINERS: Add file patterns for ata device tree bindings
Date: Fri, 27 May 2016 11:26:33 -0400 [thread overview]
Message-ID: <20160527152633.GK23194@mtj.duckdns.org> (raw)
In-Reply-To: <1463907991-7916-25-git-send-email-geert@linux-m68k.org>
On Sun, May 22, 2016 at 11:06:01AM +0200, Geert Uytterhoeven wrote:
> Submitters of device tree binding documentation may forget to CC
> the subsystem maintainer if this is missing.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: linux-ide@vger.kernel.org
Applied to libata/for-4.8.
Thanks.
--
tejun
prev parent reply other threads:[~2016-05-27 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1463907991-7916-1-git-send-email-geert@linux-m68k.org>
2016-05-22 9:06 ` [PATCH 24/54] MAINTAINERS: Add file patterns for ata device tree bindings Geert Uytterhoeven
2016-05-27 15:26 ` Tejun Heo [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=20160527152633.GK23194@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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