From: Adrian Bunk <bunk@kernel.org>
To: Li Yang <LeoLi@freescale.com>
Cc: Jeff Garzik <jeff@garzik.org>,
linuxppc-dev@ozlabs.org,
Kalra Ashish <ashish.kalra@freescale.com>,
linux-ide@vger.kernel.org,
"Robert P. J. Day" <rpjday@crashcourse.ca>
Subject: Re: [2.6 patch] sata_fsl.c: fix 8315DS workaround
Date: Mon, 4 Aug 2008 12:22:15 +0300 [thread overview]
Message-ID: <20080804092215.GE6088@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <A94B04433DF4F44C9C2AB5DEFBF29A4E05E1E7@zch01exm26.fsl.freescale.net>
On Mon, Aug 04, 2008 at 04:55:37PM +0800, Li Yang wrote:
> > -----Original Message-----
> > From: Adrian Bunk [mailto:bunk@kernel.org]
> > Sent: Monday, August 04, 2008 4:46 PM
> > To: Kalra Ashish; Li Yang; Jeff Garzik; galak@kernel.crashing.org
> > Cc: linuxppc-dev@ozlabs.org; linux-ide@vger.kernel.org;
> > Robert P. J. Day
> > Subject: [2.6 patch] sata_fsl.c: fix 8315DS workaround
> >
> > Commit e7eac96e8f0e57a6e9f94943557bc2b23be31471
> > (ata/sata_fsl: Move MPC8315DS link speed limit workaround to
> > specific ifdef) aimed at limiting the workaround only to the
> > affected hardware, but since the #ifdef used a nonexisting
> > kconfig variable it actually killed the workaround.
>
> This workaround is only for MPC8315_DS board which is not supported in the main line yet. We can remove the workaround if we need to do something here.
Thanks, in this case my patch is complete crap.
There's no need for any action.
> - Leo
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2008-08-04 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 8:46 [2.6 patch] sata_fsl.c: fix 8315DS workaround Adrian Bunk
2008-08-04 8:55 ` Li Yang
2008-08-04 9:22 ` Adrian Bunk [this message]
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=20080804092215.GE6088@cs181140183.pp.htv.fi \
--to=bunk@kernel.org \
--cc=LeoLi@freescale.com \
--cc=ashish.kalra@freescale.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rpjday@crashcourse.ca \
/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