From: Olof Johansson <olof@lixom.net>
To: Tony Prisk <linux@prisktech.co.nz>
Cc: linux-arm-kernel@lists.infradead.org, arm@kernel.org,
linux-kernel@vger.kernel.org,
vt8500-wm8505-linux-kernel@googlegroups.com
Subject: Re: [PATCH 0/4] arm: vt8500: Add support for Wondermedia WM8750/WM8850
Date: Fri, 11 Jan 2013 13:56:59 -0800 [thread overview]
Message-ID: <20130111215659.GA16521@quad.lixom.net> (raw)
In-Reply-To: <1357935162-7672-1-git-send-email-linux@prisktech.co.nz>
Hi,
On Sat, Jan 12, 2013 at 09:12:38AM +1300, Tony Prisk wrote:
> The following changes since commit a49f0d1ea3ec94fc7cf33a7c36a16343b74bd565:
>
> Linux 3.8-rc1 (2012-12-21 17:19:00 -0800)
>
> are available in the git repository at:
>
> git://server.prisktech.co.nz/git/linuxwmt.git tags/armsoc-3.9
>
> for you to fetch changes up to 82c8f175662873f7f7f4c78698888ee963d7d967:
>
> arm: vt8500: Remove remaining mach includes (2012-12-28 21:05:19 +1300)
>
> ----------------------------------------------------------------
> arm: vt8500: Add support for WM8750/WM8850. Cleanup multiplatform changes
>
> This patchset adds support for the WM8750 (ARMv6) and WM8850 (ARMv7), and
> cleans up changes for multiplatform configuration.
>
> Single platform Kconfig options are removed, along with the remaining
> mach/includes.
>
> The debug-macro.s is moved to arm/include/debug/ to allow DEBUG_LL on
> multi-platform.
>
> Signed-off-by: Tony Prisk <linux@prisktech.co.nz>
>
> ----------------------------------------------------------------
> Tony Prisk (4):
> arm: vt8500: Add support for Wondermedia WM8750/WM8850
> arm: vt8500: Remove single platform Kconfig options
> arm: vt8500: Convert debug-macro.S to be multiplatform friendly
> arm: vt8500: Remove remaining mach includes
The first patch adds some Kconfig entries, and the second one removes them.
Also, all but the first patch are really about multiplatform enablement.
I suggest that you split off the last three (and rebase them to be
independent), and apply them to a multiplatform branch for vt8500. Then the
last one is a soc branch that goes on top of the multiplatform branch (i.e. you
build it on top of multiplatform). That way we can pull in the multiplatform
changes together with those for other platforms, and then take the wm8{7,8}50
branch goes in with the other new-soc support from other platforms.
Does that make sense? I'll be happy to provide more explanation if it doesn't.
-Olof
next prev parent reply other threads:[~2013-01-11 21:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 20:12 Tony Prisk
2013-01-11 20:12 ` [PATCH 1/4] " Tony Prisk
2013-01-11 20:12 ` [PATCH 2/4] arm: vt8500: Remove single platform Kconfig options Tony Prisk
2013-01-11 20:12 ` [PATCH 3/4] arm: vt8500: Convert debug-macro.S to be multiplatform friendly Tony Prisk
2013-01-11 20:12 ` [PATCH 4/4] arm: vt8500: Remove remaining mach includes Tony Prisk
2013-01-11 21:56 ` Olof Johansson [this message]
2013-01-12 3:07 ` [PATCH 0/4] arm: vt8500: Add support for Wondermedia WM8750/WM8850 Tony Prisk
2013-01-12 3:09 ` Tony Prisk
2013-01-12 3:09 ` Tony Prisk
2013-01-12 17:12 ` Olof Johansson
2013-01-12 17:12 ` Olof Johansson
2013-01-12 17:16 ` Olof Johansson
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=20130111215659.GA16521@quad.lixom.net \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@prisktech.co.nz \
--cc=vt8500-wm8505-linux-kernel@googlegroups.com \
/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
all inboxes | Powered by JetHome®