From: Alan Curry <pacman@TheWorld.com>
To: akpm@linux-foundation.org (Andrew Morton)
Cc: benh@kernel.crashing.org (Benjamin Herrenschmidt),
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Pegasos keyboard detection
Date: Fri, 27 Jul 2007 00:48:01 -0400 (EDT) [thread overview]
Message-ID: <200707270448.l6R4m1O31531714@shell01.TheWorld.com> (raw)
In-Reply-To: <20070726212241.032e9755.akpm@linux-foundation.org> from "Andrew Morton" at Jul 26, 2007 09:22:41 PM
Andrew Morton writes the following:
>> >
>> > Did this get merged, or otherwise fixed? Even though the code in there has
>> > changed quite a bit, it looks to my untrained eye like the fix is still
>> > applicable?
>>
>> Merged a fixed version:
>>
>> f5d834fc34e61f1a40435981062000e5d2b2baa8
>>
>> (In linus tree as of now)
>
>I hope so. Alan's patch looks rather different from what you have now:
>fall back to of_find_node_by_name() if of_find_node_by_type() failed.
>
Looking at it via gitweb, I think the commit mentioned above is actually the
same as what I submitted. The diff context lines are different because there
was a similar patch in between the 2.6.22 release and my patch, which
apparently fixed the same problem on a different type of machine. It looks
like these 2 workarounds will function independently of each other.
The first 8042-detection fix was:
db0dbae9d9680bce69fe1ce775709e60c8ee9c29
And mine is:
f5d834fc34e61f1a40435981062000e5d2b2baa8
--
Alan Curry
pacman@world.std.com
next prev parent reply other threads:[~2007-07-27 4:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 6:16 keyboard not found in 2.6.22.1 Alan Curry
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 [this message]
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
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=200707270448.l6R4m1O31531714@shell01.TheWorld.com \
--to=pacman@theworld.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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
Powered by JetHome