From: Tobias <mailing54@plzk.org>
To: Len Brown <lenb@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.34-rc4
Date: Wed, 14 Apr 2010 23:05:15 +0200 [thread overview]
Message-ID: <4BC62E0B.3090006@plzk.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1004141645440.3932@localhost.localdomain>
Len Brown wrote:
>
> It is likely that this is already bisected
> and fixed by the patch here:
> https://bugzilla.kernel.org/show_bug.cgi?id=15749
>
Doh, indeed it looks like it. So far I have
git bisect start
# good: [2eaa9cfdf33b8d7fb7aff27792192e0019ae8fc6] Linux 2.6.34-rc3
git bisect good 2eaa9cfdf33b8d7fb7aff27792192e0019ae8fc6
# bad: [0d0fb0f9c5fddef4a10242fe3337f00f528a3099] Linux 2.6.34-rc4
git bisect bad 0d0fb0f9c5fddef4a10242fe3337f00f528a3099
# good: [14e71e4fb94c340273534a6d7f210aa82a3ca717] Merge
git://git.kernel.org/pub/scm/linux/kernel/git/wim/linux-2.6-watchdog
git bisect good 14e71e4fb94c340273534a6d7f210aa82a3ca717
# bad: [2f10ffcfb28beb35137d9e86992c771b4a6c5f2a] Merge branch
'drm-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6
git bisect bad 2f10ffcfb28beb35137d9e86992c771b4a6c5f2a
# good: [fb1ae635772d679eb312fa447290fc02cd0e4cf1] Merge branch
'x86-fixes-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-tip
git bisect good fb1ae635772d679eb312fa447290fc02cd0e4cf1
# bad: [d620a7cf05d4f12f5bbb1060d766e8139ab31458] Merge branch
'upstream-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev
git bisect bad d620a7cf05d4f12f5bbb1060d766e8139ab31458
# good: [f5284e7635787224dda1a2bf82a4c56b1c75671f] Merge
git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-for-linus
git bisect good f5284e7635787224dda1a2bf82a4c56b1c75671f
# bad: [c25f7cf2032aaac9bd50d6eee982719878538082] Merge branches
'battery', 'bugzilla-14667', 'bugzilla-15096', 'bugzilla-15480',
'bugzilla-15521', 'bugzilla-15605', 'gpe-reference-counters', 'misc',
'pxm-fix' and 'video-random-key' into release
git bisect bad c25f7cf2032aaac9bd50d6eee982719878538082
At least I got a free bisect turorial and will know my way next time.
Thanks and sorry for the noice.
Tobias
next prev parent reply other threads:[~2010-04-14 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 2:16 Linux 2.6.34-rc4 Linus Torvalds
2010-04-13 2:42 ` Justin P. mattock
2010-04-14 8:38 ` Tobias
2010-04-14 14:46 ` Linus Torvalds
2010-04-14 20:47 ` Len Brown
2010-04-14 21:05 ` Tobias [this message]
2010-04-14 21:32 ` Harald Arnesen
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=4BC62E0B.3090006@plzk.org \
--to=mailing54@plzk.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.