From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ARM: PRIMA2: make mach-prima2 common for all SiRF series SoC
Date: Tue, 21 Aug 2012 10:16:22 +0000 [thread overview]
Message-ID: <201208211016.22511.arnd@arndb.de> (raw)
In-Reply-To: <CAGsJ_4zBEgexWBWsKCe2UtfP1m7BSMO9dq8thi3oQVYsq22v+A@mail.gmail.com>
On Tuesday 21 August 2012, Barry Song wrote:
> i would think merging several SoCs into a dir still needs much time.
> if the whole rename is too aggresive for the moment, how about keeping
> the mach-prima2 temporarily, but this prima2 dir will also include the
> coming Marco stuff?
>
Yes, that is what I meant. Sorry if I wasn't clear on that. Please send
the marco patches adding the code in the mach-prima2 directory.
Arnd
next prev parent reply other threads:[~2012-08-21 10:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 8:19 [PATCH 0/3] ARM: PRIMA2: some patches prepared to support new SiRF SoCs Barry Song
2012-08-20 8:19 ` [PATCH 1/3] ARM: PRIMA2: use DT_MACHINE_START and convert to generic board Barry Song
2012-08-20 20:56 ` Arnd Bergmann
2012-08-21 1:49 ` Barry Song
2012-08-21 7:53 ` Arnd Bergmann
2012-08-21 8:26 ` Barry Song
2012-08-21 8:44 ` Arnd Bergmann
2012-08-20 8:19 ` [PATCH 2/3] ARM: PRIMA2: make mach-prima2 common for all SiRF series SoC Barry Song
2012-08-20 21:06 ` Arnd Bergmann
2012-08-21 1:56 ` Barry Song
2012-08-21 7:57 ` Arnd Bergmann
2012-08-21 9:16 ` Barry Song
2012-08-21 9:20 ` Arnd Bergmann
2012-08-28 6:15 ` Barry Song
2012-08-28 8:08 ` Barry Song
2012-08-28 14:28 ` Stephen Warren
2012-08-28 14:57 ` Barry Song
2012-08-21 9:29 ` Barry Song
2012-08-21 10:16 ` Arnd Bergmann [this message]
2012-08-21 2:06 ` Barry Song
2012-08-21 7:55 ` Arnd Bergmann
2012-08-20 8:19 ` [PATCH 3/3] ARM: SIRF: make sirf irqchip driver selectable since new SoCs will have GIC Barry Song
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=201208211016.22511.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.