All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: Add arm-soc tree entry
Date: Thu, 25 Oct 2012 14:24:55 +0000	[thread overview]
Message-ID: <201210251424.55290.arnd@arndb.de> (raw)
In-Reply-To: <1351101629-11826-1-git-send-email-sboyd@codeaurora.org>

On Wednesday 24 October 2012, Stephen Boyd wrote:
> Document the arm-soc tree in the maintainers file so that
> developers know how arm SoC development is structured.
> 
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>

Applied to fixes branch, I think it's reasonable to not have
to wait for 3.8.

Thanks!

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Stephen Boyd <sboyd@codeaurora.org>,
	arm@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add arm-soc tree entry
Date: Thu, 25 Oct 2012 14:24:55 +0000	[thread overview]
Message-ID: <201210251424.55290.arnd@arndb.de> (raw)
In-Reply-To: <1351101629-11826-1-git-send-email-sboyd@codeaurora.org>

On Wednesday 24 October 2012, Stephen Boyd wrote:
> Document the arm-soc tree in the maintainers file so that
> developers know how arm SoC development is structured.
> 
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>

Applied to fixes branch, I think it's reasonable to not have
to wait for 3.8.

Thanks!

	Arnd

  reply	other threads:[~2012-10-25 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 18:00 [PATCH] MAINTAINERS: Add arm-soc tree entry Stephen Boyd
2012-10-24 18:00 ` Stephen Boyd
2012-10-25 14:24 ` Arnd Bergmann [this message]
2012-10-25 14:24   ` Arnd Bergmann

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=201210251424.55290.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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 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.