From: Tejun Heo <tj@kernel.org>
To: Martin Hicks <mort@bork.org>
Cc: Scott Wood <scottwood@freescale.com>,
Kumar Gala <galak@kernel.crashing.org>,
linuxppc-dev@lists.ozlabs.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] sata-fsl: Apply link speed limits
Date: Mon, 2 Mar 2015 12:09:22 -0500 [thread overview]
Message-ID: <20150302170922.GK17694@htj.duckdns.org> (raw)
In-Reply-To: <20150219200547.GA25730@darwin.bork.org>
On Thu, Feb 19, 2015 at 03:05:47PM -0500, Martin Hicks wrote:
>
>
> The driver was ignoring limits requested by libata.force. The output
> would look like:
>
> fsl-sata ffe18000.sata: Sata FSL Platform/CSB Driver init
> ata1: FORCE: PHY spd limit set to 1.5Gbps
> ata1: SATA max UDMA/133 irq 74
> ata1: Signature Update detected @ 0 msecs
> ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 310)
>
> Signed-off-by: Martin Hicks <mort@bork.org>
Applied to libata/for-4.0-fixes.
Thanks.
--
tejun
prev parent reply other threads:[~2015-03-02 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 20:05 [PATCH] sata-fsl: Apply link speed limits Martin Hicks
2015-03-02 17:09 ` Tejun Heo [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=20150302170922.GK17694@htj.duckdns.org \
--to=tj@kernel.org \
--cc=galak@kernel.crashing.org \
--cc=linux-ide@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mort@bork.org \
--cc=scottwood@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 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).