From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Ingo Molnar <mingo@elte•hu>
Cc: Thomas Gleixner <tglx@linutronix•de>,
"H. Peter Anvin" <hpa@zytor•com>,
linux-next@vger•kernel.org
Subject: Re: linux-next: x86 tree build failure
Date: Wed, 18 Jun 2008 15:04:52 +1000 [thread overview]
Message-ID: <20080618150452.43ea6993.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080617055816.GA13556@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
Hi Ingo,
On Tue, 17 Jun 2008 07:58:16 +0200 Ingo Molnar <mingo@elte•hu> wrote:
>
> hm, i guess you mean you went back to the previous version?
No, I dropped it completely, but I will try to remember that idea for
next time. It is back today and seems ok again. Thanks for applying
those patches.
> which makes that acpi build bug not trigger in allmodconfig. But this
> just obscures the bug.
So do the acpi guys need a push? Can I help in that?
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-06-18 5:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 3:46 linux-next: x86 tree build failure Stephen Rothwell
2008-06-17 5:58 ` Ingo Molnar
2008-06-17 6:08 ` Ingo Molnar
2008-06-17 6:45 ` Ingo Molnar
2008-06-18 5:04 ` Stephen Rothwell [this message]
2008-06-18 6:39 ` Ingo Molnar
2008-06-25 3:17 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2008-07-17 2:07 Stephen Rothwell
2008-07-17 9:23 ` Vegard Nossum
2008-07-18 20:10 ` Ingo Molnar
2008-07-18 20:12 ` Ingo Molnar
2008-07-19 12:11 ` Stephen Rothwell
2008-08-25 10:22 Stephen Rothwell
2008-08-25 10:28 ` Ingo Molnar
2008-09-11 23:56 Stephen Rothwell
2008-09-12 6:05 ` Joerg Roedel
2008-09-12 7:31 ` Stephen Rothwell
2008-09-12 7:54 ` Joerg Roedel
2008-09-12 8:30 ` Ingo Molnar
2008-09-14 19:52 ` Stephen Rothwell
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=20080618150452.43ea6993.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=hpa@zytor$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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