From: Tejun Heo <tj@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: bcm-kernel-feedback-list@broadcom.com,
Kishon Vijay Abraham I <kishon@ti.com>,
Heiko Stuebner <heiko@sntech.de>,
Srinath Mannam <srinath.mannam@broadcom.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Vivek Gautam <vivek.gautam@codeaurora.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
"open list:LIBATA SUBSYSTEM (Serial and Parallel ATA drivers)"
<linux-ide@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] ata: ahci_brcm: Recover from failures to identify devices
Date: Tue, 16 Jan 2018 08:09:32 -0800 [thread overview]
Message-ID: <20180116160932.GP3460072@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <1515720668-4860-1-git-send-email-f.fainelli@gmail.com>
On Thu, Jan 11, 2018 at 05:31:06PM -0800, Florian Fainelli wrote:
> Hi Tejun, Kishon,
>
> This patch series implement a recovery mechanism to work around a HW bug
> on Broadcom AHCI SATA controller subject to noise triggering a failure to
> identify hard drives.
>
> I would like to make this this is okay with you as an approach on how to solve
> this.
>
> This should likely go through Tejun's tree to make sure the SATA controller
> and PHY changes are bundled together.
libata part looks good to me. Once phy side gets acked, I'll route
both through libata.
Thanks.
--
tejun
next prev parent reply other threads:[~2018-01-16 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 1:31 [PATCH v2 0/2] ata: ahci_brcm: Recover from failures to identify devices Florian Fainelli
2018-01-12 1:31 ` [PATCH v2 1/2] phy: brcm-sata: Implement calibrate callback Florian Fainelli
2018-01-17 5:19 ` Kishon Vijay Abraham I
2018-01-12 1:31 ` [PATCH v2 2/2] ata: ahci_brcm: Recover from failures to identify devices Florian Fainelli
2018-01-16 16:09 ` Tejun Heo [this message]
2018-01-17 15:53 ` [PATCH v2 0/2] " Tejun Heo
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=20180116160932.GP3460072@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@oracle.com \
--cc=f.fainelli@gmail.com \
--cc=heiko@sntech.de \
--cc=kishon@ti.com \
--cc=krzk@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinath.mannam@broadcom.com \
--cc=vivek.gautam@codeaurora.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