LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: cliff white <cliffw@osdl.org>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Keyboard broken on iBook - linuxppc-2.5 latest
Date: Mon, 06 Oct 2003 22:13:12 +0200	[thread overview]
Message-ID: <1065471191.30751.0.camel@gaston> (raw)
In-Reply-To: <20031006125829.58943956.cliffw@osdl.org>


On Mon, 2003-10-06 at 21:58, cliff white wrote:
> Symptoms are identical to those reported on Bugzilla Bug #1025
>
> Kernel: lastest from ppc.bkbits.net/linuxppc-2.5
> (10/06/03 AM)

Fixed in my tree, I'll send to Linus this week hopefully, after
-test7 is released

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-10-06 20:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06 19:58 Keyboard broken on iBook - linuxppc-2.5 latest cliff white
2003-10-06 20:13 ` Benjamin Herrenschmidt [this message]
2003-10-06 20:24   ` cliff white
2003-10-06 20:27     ` Benjamin Herrenschmidt
2003-10-06 22:37       ` cliff white

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=1065471191.30751.0.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=cliffw@osdl.org \
    --cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox