From: Pavel Machek <pavel@ucw.cz>
To: Miles Lane <miles.lane@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
Sylvain Meyer <sylvain.meyer@worldonline.fr>,
linux-fbdev@vger.kernel.org
Subject: Re: 2.6.33-rc3 -- Intel 945GME (inteldrmfb) -- Two Tux images
Date: Sat, 09 Jan 2010 10:34:55 +0000 [thread overview]
Message-ID: <20100109103454.GA1458@ucw.cz> (raw)
In-Reply-To: <a44ae5cd1001061035n65b5a41flc84a81285df4279c@mail.gmail.com>
On Wed 2010-01-06 13:35:59, Miles Lane wrote:
> On Wed, Jan 6, 2010 at 1:07 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> > On Wed, 2010-01-06 at 12:16 -0500, Miles Lane wrote:
> >> For a long time I have gotten two pictures of Tux showing up when I
> >> include the Tux display option in my custom kernel builds.
> >
> > Doesn't it show one for each cpu in the system?
>
> I know this is cosmetic, but could we change this behavior and just
> show one Tux on all systems? As a software tester, this just looks
Its well-known joke by now. Please keep it.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2010-01-09 10:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 17:16 2.6.33-rc3 -- Intel 945GME (inteldrmfb) -- Two Tux images displayed Miles Lane
2010-01-06 17:37 ` 2.6.33-rc3 -- Intel 945GME (inteldrmfb) -- Two Tux images James Simmons
2010-01-06 17:42 ` Miles Lane
2010-01-06 17:48 ` James Simmons
2010-01-06 18:08 ` Miles Lane
2010-01-06 17:59 ` Bruno Prémont
2010-01-06 18:06 ` Miles Lane
2010-01-06 18:07 ` Peter Zijlstra
2010-01-06 18:10 ` Miles Lane
2010-01-06 18:25 ` Peter Zijlstra
2010-01-06 18:35 ` Miles Lane
2010-01-09 10:34 ` Pavel Machek [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=20100109103454.GA1458@ucw.cz \
--to=pavel@ucw.cz \
--cc=airlied@linux.ie \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=peterz@infradead.org \
--cc=sylvain.meyer@worldonline.fr \
/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).