From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL v3] Renesas ARM-based SoC boards for v3.8 #2
Date: Tue, 13 Nov 2012 10:01:48 +0000 [thread overview]
Message-ID: <20121113100144.GX18224@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201211130848.03800.arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]
On Tue, Nov 13, 2012 at 08:48:03AM +0000, Arnd Bergmann wrote:
> On Tuesday 13 November 2012, Mark Brown wrote:
> > Please never pull anything from me unless there's a signed tag for it,
> > anything else I won't know about and may be rebased or vanish or
> > something.
> Ok, thanks for the reminder. Do you have a signed tag containing ab6f6d8521?
Nope, your e-mail was the first I'd heard of the cross-merge. I guess I
could create one if this is going to get redone for some reason...
> > > I have taken Mark on Cc to let him know about the dependency now, and I've
> > > merged ab6f6d85210c4d0265cf48e9958c04e08595055a (which has only shmobile
> > > specific ASoC patches) into the next/boards2 branch before merging your
> > > branch. This is still not perfect because it breaks bisection, but it's
> > > the best I could do aside from forcing you do do another round-trip.
> > What's the bisection problem?
> I merged ab6f6d8521 first, and then Simon's branch, which means that the
> linear (first-parent) history is ok, but bisecting the entire state of
> the tree may end up in a commit in his branch in a state before it was
> merged into mine, where it doesn't contain the patches it depends on,
> and as Simon mentioned in his pull request, that will cause a build
> failure.
Oh, I'd missed the fact that this wasn't coming in via a merge into
Simon's tree.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-13 10:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 0:40 [GIT PULL v3] Renesas ARM-based SoC boards for v3.8 Simon Horman
2012-11-01 0:40 ` [PATCH 1/8] ARM: shmobile: kzm9g: enable magnetometer ak8975 Simon Horman
2012-11-01 0:40 ` [PATCH 2/8] ARM: shmobile: kzm9g: enable three-axis digital accelerometer ADXL345 Simon Horman
2012-11-01 0:40 ` [PATCH 3/8] ARM: shmobile: kzm9g: enable DMAEngine on SHDI0 and SDHI2 Simon Horman
2012-11-01 0:40 ` [PATCH 4/8] ARM: shmobile: armadillo800eva: enable restart Simon Horman
2012-11-01 0:40 ` [PATCH 5/8] ARM: shmobile: marzen: add HSPI support Simon Horman
2012-11-01 0:40 ` [PATCH 6/8] ARM: mach-shmobile: Use DT_MACHINE for mackerel Simon Horman
2012-11-01 0:40 ` [PATCH 7/8] ARM: shmobile: Remove G3EVM machine support Simon Horman
2012-11-01 0:40 ` [PATCH 8/8] ARM: shmobile: Remove G4EVM " Simon Horman
2012-11-06 2:32 ` [GIT PULL v3] Renesas ARM-based SoC boards for v3.8 Simon Horman
2012-11-06 14:07 ` Olof Johansson
2012-11-09 7:31 ` [GIT PULL v3] Renesas ARM-based SoC boards for v3.8 #2 Simon Horman
2012-11-09 7:31 ` [PATCH 1/7] ARM: shmobile: marzen: add USB phy support Simon Horman
2013-03-13 21:19 ` Sergei Shtylyov
2013-03-14 0:44 ` Kuninori Morimoto
2013-03-14 13:20 ` Sergei Shtylyov
2012-11-09 7:31 ` [PATCH 2/7] ARM: shmobile: marzen: add USB EHCI driver support Simon Horman
2013-03-13 20:44 ` Sergei Shtylyov
2013-03-14 0:29 ` Kuninori Morimoto
2013-03-14 1:09 ` Kuninori Morimoto
2013-03-14 13:42 ` Sergei Shtylyov
2013-03-15 0:52 ` Kuninori Morimoto
2013-03-15 12:51 ` Sergei Shtylyov
2012-11-09 7:31 ` [PATCH 3/7] ARM: shmobile: marzen: add USB OHCI " Simon Horman
2012-11-09 7:31 ` [PATCH 4/7] ARM: shmobile: mackerel: enable DMAEngine on USB Host Simon Horman
2012-11-09 7:31 ` [PATCH 5/7] ARM: shmobile: use FSI driver's audio clock on armadillo800eva Simon Horman
2012-11-09 7:31 ` [PATCH 6/7] ARM: shmobile: use FSI driver's audio clock on mackerel Simon Horman
2012-11-09 7:31 ` [PATCH 7/7] ARM: shmobile: use FSI driver's audio clock on ap4evb Simon Horman
2012-11-12 21:11 ` [GIT PULL v3] Renesas ARM-based SoC boards for v3.8 #2 Arnd Bergmann
2012-11-13 2:58 ` Simon Horman
2012-11-13 5:36 ` Mark Brown
2012-11-13 8:48 ` Arnd Bergmann
2012-11-13 10:01 ` Mark Brown [this message]
2012-11-13 10:27 ` Arnd Bergmann
2012-11-14 2:15 ` Mark Brown
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=20121113100144.GX18224@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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).