From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/5] phy: Add support for NS2 SATA3 PHY in Broadcom SATA3 PHY driver
Date: Mon, 28 Mar 2016 18:31:20 -0700 [thread overview]
Message-ID: <56F9DAE8.9050204@gmail.com> (raw)
In-Reply-To: <1459140510-5317-3-git-send-email-anup.patel@broadcom.com>
Le 27/03/2016 21:48, Anup Patel a ?crit :
> This patch adds support for Broadcom NS2 SATA3 PHY in existing
> Broadcom SATA3 PHY driver.
>
> Signed-off-by: Anup Patel <anup.patel@broadcom.com>
As mentioned before during the internal review, there is a lot of churn
done here to add NS2 support, which in itself could be a good 2-3
independent preliminary patches. I tested v1 on a 7445 and did not see
any issues with it so and convinced myself your transformation is
correct so:
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2016-03-29 1:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 4:48 [PATCH v2 0/5] Add SATA3 support for Broadcom NS2 SVK Anup Patel
2016-03-28 4:48 ` [PATCH v2 1/5] phy: Rename phy-brcmstb-sata driver to phy-brcm-sata driver Anup Patel
2016-03-29 1:24 ` Florian Fainelli
2016-04-13 13:58 ` Kishon Vijay Abraham I
2016-04-14 3:13 ` Anup Patel
2016-03-28 4:48 ` [PATCH v2 2/5] phy: Add support for NS2 SATA3 PHY in Broadcom SATA3 PHY driver Anup Patel
2016-03-29 1:31 ` Florian Fainelli [this message]
2016-03-28 4:48 ` [PATCH v2 3/5] dt-bindings: phy: bindings document for common " Anup Patel
2016-03-29 1:27 ` Florian Fainelli
2016-03-28 4:48 ` [PATCH v2 4/5] dt-bindings: ata: add compatible string for iProc AHCI controller Anup Patel
2016-03-29 1:28 ` Florian Fainelli
2016-03-30 18:50 ` Tejun Heo
2016-03-28 4:48 ` [PATCH v2 5/5] arm64: dts: Add SATA3 AHCI and SATA3 PHY DT nodes for NS2 Anup Patel
2016-04-29 8:36 ` [PATCH v2 0/5] Add SATA3 support for Broadcom NS2 SVK Kishon Vijay Abraham I
2016-04-29 16:41 ` Florian Fainelli
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=56F9DAE8.9050204@gmail.com \
--to=f.fainelli@gmail.com \
--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).