From: Paul Mundt <lethal@linux-sh.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/08] mach-shmobile: Emma Mobile EV2 support V3
Date: Mon, 11 Jun 2012 03:55:43 +0000 [thread overview]
Message-ID: <20120611035543.GD10170@linux-sh.org> (raw)
In-Reply-To: <20120516064449.32286.77941.sendpatchset@w520>
On Wed, May 16, 2012 at 03:44:49PM +0900, Magnus Damm wrote:
> mach-shmobile: Emma Mobile EV2 support V3
>
> [PATCH 01/08] mach-shmobile: Emma Mobile EV2 SoC base support V3
> [PATCH 02/08] ARM: Undelete KZM9D mach-type V3
> [PATCH 03/08] mach-shmobile: KZM9D board support V3
> [PATCH 04/08] mach-shmobile: Emma Mobile EV2 SMP support V3
> [PATCH 05/08] mach-shmobile: Emma Mobile EV2 GPIO support V3
> [PATCH 06/08] mach-shmobile: KZM9D board Ethernet support V3
> [PATCH 07/08] mach-shmobile: Emma Mobile EV2 DT support V3
> [PATCH 08/08] mach-shmobile: Use DT_MACHINE for KZM9D V3
>
Now that this series has hit mainline I notice that no defconfig is
available for the board, so there's no way to have any coverage in it in
-next. When we're at a point where multiple boards are enabled in one
config then they can be consolidated, but it's not acceptable to have a
platform upstream that people have no way of building.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, horms@verge.net.au,
linux@arm.linux.org.uk, arnd@arndb.de, linux-sh@vger.kernel.org,
linux-kernel@vger.kernel.org, rjw@sisk.pl, olof@lixom.net
Subject: Re: [PATCH 00/08] mach-shmobile: Emma Mobile EV2 support V3
Date: Mon, 11 Jun 2012 12:55:43 +0900 [thread overview]
Message-ID: <20120611035543.GD10170@linux-sh.org> (raw)
In-Reply-To: <20120516064449.32286.77941.sendpatchset@w520>
On Wed, May 16, 2012 at 03:44:49PM +0900, Magnus Damm wrote:
> mach-shmobile: Emma Mobile EV2 support V3
>
> [PATCH 01/08] mach-shmobile: Emma Mobile EV2 SoC base support V3
> [PATCH 02/08] ARM: Undelete KZM9D mach-type V3
> [PATCH 03/08] mach-shmobile: KZM9D board support V3
> [PATCH 04/08] mach-shmobile: Emma Mobile EV2 SMP support V3
> [PATCH 05/08] mach-shmobile: Emma Mobile EV2 GPIO support V3
> [PATCH 06/08] mach-shmobile: KZM9D board Ethernet support V3
> [PATCH 07/08] mach-shmobile: Emma Mobile EV2 DT support V3
> [PATCH 08/08] mach-shmobile: Use DT_MACHINE for KZM9D V3
>
Now that this series has hit mainline I notice that no defconfig is
available for the board, so there's no way to have any coverage in it in
-next. When we're at a point where multiple boards are enabled in one
config then they can be consolidated, but it's not acceptable to have a
platform upstream that people have no way of building.
WARNING: multiple messages have this Message-ID (diff)
From: lethal@linux-sh.org (Paul Mundt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/08] mach-shmobile: Emma Mobile EV2 support V3
Date: Mon, 11 Jun 2012 12:55:43 +0900 [thread overview]
Message-ID: <20120611035543.GD10170@linux-sh.org> (raw)
In-Reply-To: <20120516064449.32286.77941.sendpatchset@w520>
On Wed, May 16, 2012 at 03:44:49PM +0900, Magnus Damm wrote:
> mach-shmobile: Emma Mobile EV2 support V3
>
> [PATCH 01/08] mach-shmobile: Emma Mobile EV2 SoC base support V3
> [PATCH 02/08] ARM: Undelete KZM9D mach-type V3
> [PATCH 03/08] mach-shmobile: KZM9D board support V3
> [PATCH 04/08] mach-shmobile: Emma Mobile EV2 SMP support V3
> [PATCH 05/08] mach-shmobile: Emma Mobile EV2 GPIO support V3
> [PATCH 06/08] mach-shmobile: KZM9D board Ethernet support V3
> [PATCH 07/08] mach-shmobile: Emma Mobile EV2 DT support V3
> [PATCH 08/08] mach-shmobile: Use DT_MACHINE for KZM9D V3
>
Now that this series has hit mainline I notice that no defconfig is
available for the board, so there's no way to have any coverage in it in
-next. When we're at a point where multiple boards are enabled in one
config then they can be consolidated, but it's not acceptable to have a
platform upstream that people have no way of building.
next prev parent reply other threads:[~2012-06-11 3:55 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 6:44 [PATCH 00/08] mach-shmobile: Emma Mobile EV2 support V3 Magnus Damm
2012-05-16 6:44 ` Magnus Damm
2012-05-16 6:44 ` Magnus Damm
2012-05-16 6:44 ` [PATCH 01/08] mach-shmobile: Emma Mobile EV2 SoC base " Magnus Damm
2012-05-16 6:44 ` Magnus Damm
2012-05-16 6:44 ` Magnus Damm
2012-05-16 6:56 ` Paul Mundt
2012-05-16 6:56 ` Paul Mundt
2012-05-16 6:56 ` Paul Mundt
2012-05-16 9:49 ` Magnus Damm
2012-05-16 9:49 ` Magnus Damm
2012-05-16 9:49 ` Magnus Damm
2012-05-16 6:45 ` [PATCH 02/08] ARM: Undelete KZM9D mach-type V3 Magnus Damm
2012-05-16 6:45 ` Magnus Damm
2012-05-16 6:45 ` Magnus Damm
2012-05-16 6:45 ` [PATCH 03/08] mach-shmobile: KZM9D board support V3 Magnus Damm
2012-05-16 6:45 ` Magnus Damm
2012-05-16 6:45 ` Magnus Damm
2012-05-16 6:45 ` [PATCH 04/08] mach-shmobile: Emma Mobile EV2 SMP " Magnus Damm
2012-05-16 6:45 ` Magnus Damm
2012-05-16 6:45 ` Magnus Damm
2012-05-16 6:45 ` [PATCH 05/08] mach-shmobile: Emma Mobile EV2 GPIO " Magnus Damm
2012-05-16 6:45 ` Magnus Damm
2012-05-16 6:45 ` Magnus Damm
2012-05-16 6:45 ` [PATCH 06/08] mach-shmobile: KZM9D board Ethernet " Magnus Damm
2012-05-16 6:45 ` Magnus Damm
2012-05-16 6:45 ` Magnus Damm
2012-05-16 6:45 ` [PATCH 07/08] mach-shmobile: Emma Mobile EV2 DT " Magnus Damm
2012-05-16 6:45 ` Magnus Damm
2012-05-16 6:45 ` Magnus Damm
2012-05-16 6:46 ` [PATCH 08/08] mach-shmobile: Use DT_MACHINE for KZM9D V3 Magnus Damm
2012-05-16 6:46 ` Magnus Damm
2012-05-16 6:46 ` Magnus Damm
2012-05-18 1:44 ` [PATCH 00/08] mach-shmobile: Emma Mobile EV2 support V3 Simon Horman
2012-05-18 1:44 ` Simon Horman
2012-05-18 1:44 ` Simon Horman
2012-05-18 3:30 ` Simon Horman
2012-05-18 3:30 ` Simon Horman
2012-05-18 3:30 ` Simon Horman
2012-05-18 3:40 ` Magnus Damm
2012-05-18 3:40 ` Magnus Damm
2012-05-18 3:40 ` Magnus Damm
2012-05-18 4:46 ` Simon Horman
2012-05-18 4:46 ` Simon Horman
2012-05-18 4:46 ` Simon Horman
2012-06-11 3:55 ` Paul Mundt [this message]
2012-06-11 3:55 ` Paul Mundt
2012-06-11 3:55 ` Paul Mundt
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=20120611035543.GD10170@linux-sh.org \
--to=lethal@linux-sh.org \
--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.