From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Zang Roy-r61911 <tie-fei.zang@freescale.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Alexandre.Bounine@tundra.com,
Yang Xin-Xin-r48390 <Xin-Xin.Yang@freescale.com>,
Kumar Gala <galak@kernel.crashing.org>
Subject: Re: [PATCH/2.6.17-rc4 10/10] bugs fix for marvell SATA on powerp c pl atform
Date: Thu, 18 May 2006 17:37:04 -0400 [thread overview]
Message-ID: <446CE900.9070802@rtr.ca> (raw)
In-Reply-To: <446CE217.2070703@pobox.com>
Jeff Garzik wrote:
>
> I'm happy that you have an updated internal driver, but that helps no
> one else.
Yikes! Mine own words, echoed back at me!
I'll organize some patches for you Friday.
Cheers
WARNING: multiple messages have this Message-ID (diff)
From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Alexandre.Bounine@tundra.com, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>,
Yang Xin-Xin-r48390 <Xin-Xin.Yang@freescale.com>
Subject: Re: [PATCH/2.6.17-rc4 10/10] bugs fix for marvell SATA on powerp c pl atform
Date: Thu, 18 May 2006 17:37:04 -0400 [thread overview]
Message-ID: <446CE900.9070802@rtr.ca> (raw)
In-Reply-To: <446CE217.2070703@pobox.com>
Jeff Garzik wrote:
>
> I'm happy that you have an updated internal driver, but that helps no
> one else.
Yikes! Mine own words, echoed back at me!
I'll organize some patches for you Friday.
Cheers
next prev parent reply other threads:[~2006-05-18 21:37 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 4:03 [PATCH/2.6.17-rc4 10/10] bugs fix for marvell SATA on powerp c pl atform Zang Roy-r61911
2006-05-18 4:03 ` Zang Roy-r61911
2006-05-18 7:02 ` Benjamin Herrenschmidt
2006-05-18 7:02 ` Benjamin Herrenschmidt
2006-05-18 15:26 ` Jeff Garzik
2006-05-18 15:26 ` Jeff Garzik
2006-05-18 20:50 ` Mark Lord
2006-05-18 20:50 ` Mark Lord
2006-05-18 21:07 ` Jeff Garzik
2006-05-18 21:07 ` Jeff Garzik
2006-05-18 21:37 ` Mark Lord [this message]
2006-05-18 21:37 ` Mark Lord
2006-05-26 8:39 ` Sven Luther
2006-05-26 8:39 ` Sven Luther
2006-05-26 8:56 ` Jeff Garzik
2006-05-26 8:56 ` Jeff Garzik
2006-05-26 8:58 ` Sven Luther
2006-05-26 8:58 ` Sven Luther
2006-05-26 11:41 ` Mark Lord
2006-05-26 11:41 ` Mark Lord
2006-05-26 11:42 ` Sven Luther
2006-05-26 11:42 ` Sven Luther
2006-05-26 13:19 ` Mark Lord
2006-05-26 13:19 ` Mark Lord
2006-05-26 14:15 ` Sven Luther
2006-05-26 14:15 ` Sven Luther
2006-05-26 15:47 ` Mark Lord
2006-05-26 15:47 ` Mark Lord
2006-05-26 16:01 ` Sven Luther
2006-05-26 16:01 ` Sven Luther
2006-05-26 16:15 ` Sven Luther
2006-05-26 16:15 ` Sven Luther
2006-05-26 16:21 ` Mark Lord
2006-05-26 16:21 ` Mark Lord
2006-05-26 16:25 ` Sven Luther
2006-05-26 16:25 ` Sven Luther
2006-05-18 12:01 ` Ric Wheeler
2006-05-18 12:01 ` Ric Wheeler
-- strict thread matches above, loose matches on Subject: below --
2006-05-19 4:06 Zang Roy-r61911
2006-05-19 4:06 ` Zang Roy-r61911
2006-05-19 4:12 Zang Roy-r61911
2006-05-19 4:12 ` Zang Roy-r61911
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=446CE900.9070802@rtr.ca \
--to=liml@rtr.ca \
--cc=Alexandre.Bounine@tundra.com \
--cc=Xin-Xin.Yang@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=tie-fei.zang@freescale.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 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.