From: Sasha Levin <sashal@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 4.14 014/115] ata: ahci_brcm: Match BCM63138 compatible strings
Date: Thu, 21 Nov 2019 22:29:19 -0500 [thread overview]
Message-ID: <20191122032919.GL16867@sasha-vm> (raw)
In-Reply-To: <bcd8f736-34a7-b0bb-adc1-1f7a092fc1f5@gmail.com>
On Wed, Nov 13, 2019 at 12:07:25PM -0800, Florian Fainelli wrote:
>On 11/12/19 5:54 PM, Sasha Levin wrote:
>> From: Florian Fainelli <f.fainelli@gmail.com>
>>
>> [ Upstream commit fb8506f15f2e394f5f648575cf48a26e8744390c ]
>>
>> Match the "brcm,bcm63138-ahci" compatible string in order to allow this
>> driver to probe on such platforms.
>>
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>> Signed-off-by: Jens Axboe <axboe@kernel.dk>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>
>This is a feature and not really a bug fix, is someone specifically
>asking for this to be back ported? Also without the matching SATA PHY
>driver changes:
>
>7b69fa1c5c930886f8a916cc47096dd4044c007a ("phy: brcm-sata: Add BCM63138
>(DSL) PHY init sequence")
>
>this is pretty useless on its own. Same applies to all automatic
>selections, not just this kernel obviously.
Ah, I got it from a distro tree but I see the backported the driver too.
I'll drop it, thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-11-22 3:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191113015622.11592-1-sashal@kernel.org>
2019-11-13 1:54 ` [PATCH AUTOSEL 4.14 014/115] ata: ahci_brcm: Match BCM63138 compatible strings Sasha Levin
2019-11-13 20:07 ` Florian Fainelli
2019-11-22 3:29 ` Sasha Levin [this message]
2019-11-13 1:54 ` [PATCH AUTOSEL 4.14 015/115] ata: ahci_brcm: Allow using driver or DSL SoCs Sasha Levin
2019-11-13 1:55 ` [PATCH AUTOSEL 4.14 049/115] ata: ep93xx: Use proper enums for directions Sasha Levin
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=20191122032919.GL16867@sasha-vm \
--to=sashal@kernel.org \
--cc=axboe@kernel.dk \
--cc=f.fainelli@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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).