From: Vinod Koul <vkoul@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
Kishon Vijay Abraham I <kishon@ti.com>,
Rob Herring <robh+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 0/2] phy: phy-brcm-sata: Allow configuration SATA AFE TX amplitude
Date: Mon, 5 Oct 2020 11:13:33 +0530 [thread overview]
Message-ID: <20201005054333.GM2968@vkoul-mobl> (raw)
In-Reply-To: <e2ff572e-8934-bf98-0bcc-06220b277810@gmail.com>
Hi Florian,
On 04-10-20, 19:56, Florian Fainelli wrote:
>
>
> On 9/30/2020 8:19 PM, Florian Fainelli wrote:
> > Hi Kishon,
> >
> > This patch series allows the configuration of the Broadcom SATA PHY TX
> > amplitude which may be required in order to meet specific tests.
>
> Hi Vinod,
>
> Would you need me to resend these two patches? For some reason
> get_maintainers.pl did not pick up your email. If not, here are the two
> patches from lore:
Yes I dont have these in my inbox. Unfortunately it is late in the cycle
and I have already sent PR to greg for 5.10 so I am not accepting
patches till rc1. Please rebase on rc1 and resend...
> https://lore.kernel.org/linux-devicetree/20201001031916.411999-2-f.fainelli@gmail.com/
> https://lore.kernel.org/linux-devicetree/20201001031916.411999-3-f.fainelli@gmail.com/
>
> Thanks
> --
> Florian
--
~Vinod
prev parent reply other threads:[~2020-10-05 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 3:19 [PATCH 0/2] phy: phy-brcm-sata: Allow configuration SATA AFE TX amplitude Florian Fainelli
2020-10-01 3:19 ` [PATCH 1/2] dt-bindings: phy: Allow defining the " Florian Fainelli
2020-10-06 20:21 ` Rob Herring
2020-10-01 3:19 ` [PATCH 2/2] phy: phy-brcm-sata: Allow configuration " Florian Fainelli
2020-10-05 2:56 ` [PATCH 0/2] " Florian Fainelli
2020-10-05 5:43 ` Vinod Koul [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=20201005054333.GM2968@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).