linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Alan Curry <pacman@TheWorld.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Pegasos keyboard detection
Date: Mon, 6 Aug 2007 20:45:52 +0200	[thread overview]
Message-ID: <a650790070fdbccce792ea78776cf8a5@kernel.crashing.org> (raw)
In-Reply-To: <200708020440.l724edCT290676@shell01.TheWorld.com>

>> You don't need to patch Linux at all. In fact for silly things like 
>> this
>> I would recommend against it :)
>
> If the workaround doesn't go into the kernel, everybody with affected
> hardware has to individually find out about the bug (probably by 
> experiencing
> an annoying keyboardless boot) and fix it himself.

That's one of the reasons why this should go into a bootwrapper.


Segher

  reply	other threads:[~2007-08-06 18:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200707230616.l6N6GaPg1212004@shell01.TheWorld.com>
2007-07-25  1:28 ` [PATCH] powerpc: Pegasos keyboard detection Alan Curry
2007-07-25  6:22   ` Benjamin Herrenschmidt
2007-07-25  6:45     ` Alan Curry
2007-07-25  7:12   ` Benjamin Herrenschmidt
2007-07-27  1:48     ` Andrew Morton
2007-07-27  3:00       ` Benjamin Herrenschmidt
2007-07-27  4:22         ` Andrew Morton
2007-07-27  4:48           ` Alan Curry
2007-07-27  7:15           ` Benjamin Herrenschmidt
2007-07-31 21:26   ` Segher Boessenkool
2007-08-01  7:25     ` Matt Sealey
2007-08-01  7:28       ` Matt Sealey
2007-08-02  4:40       ` Alan Curry
2007-08-06 18:45         ` Segher Boessenkool [this message]
2007-08-06 21:40         ` Matt Sealey
2007-08-06 21:57           ` Segher Boessenkool
2007-08-07 16:21             ` Matt Sealey
2007-08-09 16:30               ` Segher Boessenkool
2007-08-09 16:46                 ` Matt Sealey
2007-08-07  4:16           ` Alan Curry
2007-08-07 16:27             ` Matt Sealey

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=a650790070fdbccce792ea78776cf8a5@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=pacman@TheWorld.com \
    /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).