From: Stephen Warren <swarren@wwwdotorg.org>
To: Markus Mayer <markus.mayer@linaro.org>,
Matt Porter <matt.porter@linaro.org>,
Christian Daudt <bcm@fixthebug.org>
Cc: ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: bcm2835: Move to mach-bcm directory
Date: Mon, 24 Feb 2014 19:49:24 -0700 [thread overview]
Message-ID: <530C04B4.9020204@wwwdotorg.org> (raw)
In-Reply-To: <1392941771-15774-1-git-send-email-markus.mayer@linaro.org>
On 02/20/2014 05:16 PM, Markus Mayer wrote:
> Move the bcm2835 board file into the mach-bcm directory. This allows us
> to get rid of the mach-bcm2835 directory with the associated Kconfig
> and Makefile.
I've applied this to bcm2835's for-3.15/soc branch (and squashed the
defconfig fix into it).
prev parent reply other threads:[~2014-02-25 2:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 0:16 [PATCH] ARM: bcm2835: Move to mach-bcm directory Markus Mayer
2014-02-21 4:53 ` Stephen Warren
2014-02-21 14:09 ` Matt Porter
2014-02-21 17:41 ` Markus Mayer
2014-02-21 17:48 ` Stephen Warren
2014-02-21 17:50 ` Matt Porter
2014-02-25 2:49 ` 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=530C04B4.9020204@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=bcm@fixthebug.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.mayer@linaro.org \
--cc=matt.porter@linaro.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