linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tj@kernel.org (Tejun Heo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] sata_mv: Manage SATA port multiplier while searching for active links
Date: Mon, 30 Mar 2015 13:35:15 -0400	[thread overview]
Message-ID: <20150330173515.GC9974@htj.duckdns.org> (raw)
In-Reply-To: <1427736765-846-1-git-send-email-gregory.clement@free-electrons.com>

Hello,

On Mon, Mar 30, 2015 at 07:32:45PM +0200, Gregory CLEMENT wrote:
> From: Nadav Haklai <nadavh@marvell.com>
> 
> With this patch, when searching for active link, first search through
> the port multiplier links. And then fall to the default ap active_tag
> only if no there is no active link in the port multiplier.

What does this fix?  What was broken before?  What's the impact of the
patch?  A patch description which just restates the patch content
isn't all that useful.

Thanks.

-- 
tejun

  reply	other threads:[~2015-03-30 17:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 17:32 [PATCH] sata_mv: Manage SATA port multiplier while searching for active links Gregory CLEMENT
2015-03-30 17:35 ` Tejun Heo [this message]
2015-03-31  7:15   ` Gregory CLEMENT

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=20150330173515.GC9974@htj.duckdns.org \
    --to=tj@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).