The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Rob Herring <robherring2@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org,
	Rob Herring <rob.herring@calxeda.com>
Subject: Re: [PATCH] MAINTAINERS: add scripts/dtc under Devicetree maintainers
Date: Mon, 01 Oct 2012 16:09:02 -0600	[thread overview]
Message-ID: <506A147E.3040309@wwwdotorg.org> (raw)
In-Reply-To: <1349124546-16864-1-git-send-email-robherring2@gmail.com>

On 10/01/2012 02:49 PM, Rob Herring wrote:
> From: Rob Herring <rob.herring@calxeda.com>
> 
> scripts/dtc has no explicit in kernel maintainer, so add it under
> Devicetree maintainers.

> diff --git a/MAINTAINERS b/MAINTAINERS

>  F:	Documentation/devicetree
>  F:	drivers/of
>  F:	include/linux/of*.h
> +	scripts/dtc

Doesn't that new line need to start with "F:" too?

      reply	other threads:[~2012-10-01 22:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01 20:49 [PATCH] MAINTAINERS: add scripts/dtc under Devicetree maintainers Rob Herring
2012-10-01 22:09 ` Stephen Warren [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=506A147E.3040309@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=robherring2@gmail.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