From: linux@prisktech.co.nz (Tony Prisk)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] arm: vt8500: Add support for Wondermedia WM8750/WM8850
Date: Sat, 12 Jan 2013 16:07:24 +1300 [thread overview]
Message-ID: <1357960044.8515.0.camel@gitbox> (raw)
In-Reply-To: <20130111215659.GA16521@quad.lixom.net>
> 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
I think I understand - pull requests to follow.
Tony P
next prev parent reply other threads:[~2013-01-12 3:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 20:12 [PATCH 0/4] arm: vt8500: Add support for Wondermedia WM8750/WM8850 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 ` [PATCH 0/4] arm: vt8500: Add support for Wondermedia WM8750/WM8850 Olof Johansson
2013-01-12 3:07 ` Tony Prisk [this message]
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=1357960044.8515.0.camel@gitbox \
--to=linux@prisktech.co.nz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).