From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: linux-ide@vger.kernel.org, Rupjyoti Sarmah <rsarmah@amcc.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [PATCH] 460EX on-chip SATA driver<kernel 2.6.33> < resubmission : 02>
Date: Wed, 7 Apr 2010 10:22:53 +0200 [thread overview]
Message-ID: <201004071022.53705.sr@denx.de> (raw)
In-Reply-To: <1270626116.2300.68.camel@pasglop>
On Wednesday 07 April 2010 09:41:56 Benjamin Herrenschmidt wrote:
> BTW. Stefan mentioned earlier that they had some fixes for that driver
> in the Denx tree. Are those fixes now included in that variant ?
Yes, from a first scan the fix I was referring to seems to be included.
Cheers,
Stefan
next prev parent reply other threads:[~2010-04-07 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 11:41 [PATCH] 460EX on-chip SATA driver<kernel 2.6.33> < resubmission : 02> Rupjyoti Sarmah
2010-04-06 15:16 ` Jeff Garzik
2010-04-07 7:41 ` Benjamin Herrenschmidt
2010-04-07 8:22 ` Stefan Roese [this message]
2010-04-07 7:57 ` Rupjyoti Sarmah
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=201004071022.53705.sr@denx.de \
--to=sr@denx.de \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rsarmah@amcc.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).