From: chris@printf•net (Chris Ball)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 3/4] rename ARCH_BCM to ARCH_BCM_MOBILE (mmc)
Date: Mon, 24 Mar 2014 13:29:22 +0000 [thread overview]
Message-ID: <86pplbwwr1.fsf@void.printf.net> (raw)
In-Reply-To: <20140312214524.GS25092@beef> (Matt Porter's message of "Wed, 12 Mar 2014 17:45:24 -0400")
Hi,
On Wed, Mar 12 2014, Matt Porter wrote:
> On Mon, Sep 23, 2013 at 10:20:35AM -0700, Christian Daudt wrote:
>> Currently ARCH_BCM has been used for Broadcom
>> Mobile V7 based SoCs. In order to allow other Broadcom
>> SoCs to also use mach-bcm directory and files, this patch
>> renames the original ARCH_BCM to ARCH_BCM_MOBILE, and
>> uses ARCH_BCM to define any Broadcom chip residing
>> in mach-bcm directory.
>>
>> Signed-off-by: Christian Daudt <bcm@fixthebug•org>
>> Acked-by: Olof Johansson <olof@lixom•net>
>
> Hi Chris,
>
> Could you please take this patch for 3.15? It was missed for 3.14.
Sorry about that -- it's in mmc-next for 3.15 now.
Thanks,
- Chris.
--
Chris Ball <chris@printf•net> <http://printf.net/>
next prev parent reply other threads:[~2014-03-24 13:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 17:20 [PATCH v2 0/4] ARCH_BCM rename Christian Daudt
2013-09-23 17:20 ` [PATCH v2 1/4] rename ARCH_BCM to ARCH_BCM_MOBILE (mach-bcm) Christian Daudt
2013-10-28 20:38 ` Olof Johansson
2013-10-30 6:22 ` Christian Daudt
2013-09-23 17:20 ` [PATCH v2 2/4] rename ARCH_BCM to ARCH_BCM_MOBILE (clocksource) Christian Daudt
2013-12-13 8:48 ` Daniel Lezcano
2013-12-13 16:43 ` Christian Daudt
2013-09-23 17:20 ` [PATCH v2 3/4] rename ARCH_BCM to ARCH_BCM_MOBILE (mmc) Christian Daudt
2013-12-13 17:59 ` Christian Daudt
2014-03-12 21:45 ` Matt Porter
2014-03-24 13:29 ` Chris Ball [this message]
2013-09-23 17:20 ` [PATCH v2 4/4] rename ARCH_BCM to ARCH_BCM_MOBILE (dt) Christian Daudt
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=86pplbwwr1.fsf@void.printf.net \
--to=chris@printf$(echo .)net \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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