From: ccross@android.com (Colin Cross)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Tegra i2c board changes + defconfig update
Date: Mon, 7 Mar 2011 12:07:08 -0800 [thread overview]
Message-ID: <AANLkTimWi2z30tBK_1N_6gjqgbugCeCwc1oV3zWtModj@mail.gmail.com> (raw)
In-Reply-To: <20110307200452.GM1829@sirena.org.uk>
On Mon, Mar 7, 2011 at 12:04 PM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Mon, Mar 07, 2011 at 11:59:02AM -0800, Colin Cross wrote:
>
>> linux-next. ?There shouldn't be any conflicts with linux-next, and
>> there is no need for linux-next to build after merging some of its
>> branches.
>
> -next gets built after each merge so the tree does need to merge without
> the trees that get merged later on.
Ok, we can make sure Tegra is merged after i2c and asoc, in which case
it should build fine.
next prev parent reply other threads:[~2011-03-07 20:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 8:26 [PATCH 0/3] Tegra i2c board changes + defconfig update Olof Johansson
2011-03-07 8:26 ` [PATCH 1/3] ARM: tegra: seaboard: register i2c devices Olof Johansson
2011-03-07 17:24 ` Stephen Warren
2011-03-07 19:29 ` Olof Johansson
2011-03-07 19:39 ` Stephen Warren
2011-03-07 23:26 ` Olof Johansson
2011-03-07 8:26 ` [PATCH 2/3] ARM: tegra: harmony: " Olof Johansson
2011-03-07 15:43 ` Sergei Shtylyov
2011-03-07 17:29 ` Stephen Warren
2011-03-07 8:26 ` [PATCH 3/3] ARM: tegra: enable new drivers in defconfig Olof Johansson
2011-03-07 17:34 ` Stephen Warren
2011-03-07 19:18 ` Olof Johansson
2011-03-07 19:24 ` Stephen Warren
2011-03-07 19:59 ` [PATCH 0/3] Tegra i2c board changes + defconfig update Colin Cross
2011-03-07 20:04 ` Mark Brown
2011-03-07 20:07 ` Colin Cross [this message]
2011-03-07 23:13 ` 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=AANLkTimWi2z30tBK_1N_6gjqgbugCeCwc1oV3zWtModj@mail.gmail.com \
--to=ccross@android.com \
--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).