From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: PB1176 broken in 2.6.35-rc1, bisected
Date: Wed, 2 Jun 2010 23:48:01 +0100 [thread overview]
Message-ID: <20100602224801.GA12604@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTikoCy2FH_5ICh-iiI_wzGj6D6oszyM-zCXkNC_4@mail.gmail.com>
On Thu, Jun 03, 2010 at 12:33:57AM +0200, Linus Walleij wrote:
> I bisected until I had this as the first commit causing the trouble:
>
> commit ac1d426e825ab5778995f2f6f053ca2e6b45c622
> Merge: fda0e18 a3685f0
> Author: Russell King <rmk+kernel@arm.linux.org.uk>
> Date: Mon May 17 17:24:04 2010 +0100
>
> Merge branch 'devel-stable' into devel
>
> Conflicts:
> arch/arm/Kconfig
> arch/arm/include/asm/system.h
> arch/arm/mm/Kconfig
You should be able to bisect further - did bisect just give up at this
point?
Do you know which half of that merge was also tested?
prev parent reply other threads:[~2010-06-02 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 22:33 PB1176 broken in 2.6.35-rc1, bisected Linus Walleij
2010-06-02 22:46 ` Catalin Marinas
2010-06-03 8:48 ` Linus Walleij
2010-06-03 16:15 ` Catalin Marinas
2010-06-29 0:42 ` Linus Walleij
2010-06-29 9:31 ` Catalin Marinas
2010-06-02 22:48 ` Russell King - ARM Linux [this message]
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=20100602224801.GA12604@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).