From: Timur Tabi <b04825@freescale.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linuxppc-dev <linuxppc-dev@ozlabs.org>,
the arch/x86 maintainers <x86@kernel.org>,
Parisc List <linux-parisc@vger.kernel.org>,
Wood Scott-B07421 <B07421@freescale.com>,
Kumar Gala <galak@kernel.crashing.org>
Subject: Re: Build regressions/improvements in v3.4-rc7
Date: Thu, 17 May 2012 13:44:11 -0500 [thread overview]
Message-ID: <4FB546FB.807@freescale.com> (raw)
In-Reply-To: <CAMuHMdVszy2sk6f045krqr=PPQFnd-GrtJYJMQCCPzkq-65psg@mail.gmail.com>
Geert Uytterhoeven wrote:
> powerpc randconfig
Doesn't this generate a different .config every time it's run? Do I keep
generating random .config files until the problem shows up?
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <b04825@freescale.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
Parisc List <linux-parisc@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Build regressions/improvements in v3.4-rc7
Date: Thu, 17 May 2012 13:44:11 -0500 [thread overview]
Message-ID: <4FB546FB.807@freescale.com> (raw)
In-Reply-To: <CAMuHMdVszy2sk6f045krqr=PPQFnd-GrtJYJMQCCPzkq-65psg@mail.gmail.com>
Geert Uytterhoeven wrote:
> powerpc randconfig
Doesn't this generate a different .config every time it's run? Do I keep
generating random .config files until the problem shows up?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-05-17 18:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 8:30 Build regressions/improvements in v3.4-rc7 Geert Uytterhoeven
2012-05-16 8:47 ` Geert Uytterhoeven
2012-05-16 8:47 ` Geert Uytterhoeven
2012-05-16 8:47 ` Geert Uytterhoeven
2012-05-16 14:46 ` James Bottomley
2012-05-16 14:46 ` James Bottomley
2012-05-16 15:59 ` Kasatkin, Dmitry
2012-05-16 15:59 ` Kasatkin, Dmitry
2012-05-16 15:59 ` Kasatkin, Dmitry
2012-05-16 15:59 ` Geert Uytterhoeven
2012-05-16 15:59 ` Geert Uytterhoeven
2012-05-16 15:59 ` Geert Uytterhoeven
2012-05-17 0:27 ` John David Anglin
2012-05-17 0:27 ` John David Anglin
2012-05-16 23:51 ` Benjamin Herrenschmidt
2012-05-16 23:51 ` Benjamin Herrenschmidt
2012-05-17 17:30 ` Timur Tabi
2012-05-17 17:30 ` Timur Tabi
2012-05-17 17:52 ` Tabi Timur-B04825
2012-05-17 17:52 ` Tabi Timur-B04825
2012-05-17 17:52 ` Tabi Timur-B04825
2012-05-17 18:42 ` Geert Uytterhoeven
2012-05-17 18:42 ` Geert Uytterhoeven
2012-05-17 18:42 ` Geert Uytterhoeven
2012-05-17 18:44 ` Timur Tabi [this message]
2012-05-17 18:44 ` Timur Tabi
2012-05-17 18:48 ` Scott Wood
2012-05-17 18:48 ` Scott Wood
2012-05-17 18:51 ` Timur Tabi
2012-05-17 18:51 ` Timur Tabi
2012-05-17 18:42 ` Timur Tabi
2012-05-17 18:42 ` Timur Tabi
2012-05-18 7:47 ` Michael Ellerman
2012-05-18 7:47 ` Michael Ellerman
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=4FB546FB.807@freescale.com \
--to=b04825@freescale.com \
--cc=B07421@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=x86@kernel.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.