From: "Marek Behún" <kabel@kernel.org>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: Vinod Koul <vkoul@kernel.org>,
linux-phy@lists.infradead.org, pali@kernel.org
Subject: Re: [PATCH phy v4 3/5] Revert "ata: ahci: mvebu: Make SATA PHY optional for Armada 3720"
Date: Fri, 25 Feb 2022 00:43:00 +0100 [thread overview]
Message-ID: <20220225004300.1bd1405e@thinkpad> (raw)
In-Reply-To: <c6a1d5ca-255b-9a3d-aad2-9c3dc4dd68a3@opensource.wdc.com>
On Fri, 25 Feb 2022 07:33:48 +0900
Damien Le Moal <damien.lemoal@opensource.wdc.com> wrote:
> On 2/25/22 00:37, Marek Behún wrote:
> > On Thu, 24 Feb 2022 08:14:58 -0700
> > Jens Axboe <axboe@kernel.dk> wrote:
> >
> >> On 2/24/22 8:13 AM, Marek Beh?n wrote:
> >>> Dear Jens,
> >>>
> >>> could you please send Ack for this patch?
> >>> https://lore.kernel.org/linux-phy/20220203214444.1508-4-kabel@kernel.org/
> >>>
> >>> It is a revert of another patch that was added because of potential
> >>> problems in comphy driver, and these are now solved by this series, but
> >>> Vinod says he can apply the ATA patch but he needs your Ack.
> >>
> >> I'm not maintaining libata anymore, adding Damien who's the new
> >> maintainer. Leaving email below.
> >
> > Dear Damien,
> > could you look at this revert and give your Ack? See the quoted message
> > for Jens.
>
> The patch look OK to me. But I have not received it, nor do I see it in
> linux-ide list. Please resend it to me and linux-ide so that I can apply
> it together with other libata fixes.
Dear Damien,
this needs to be applied only after the first two patches of that
series are applied via linux-phy, so we would like all of them to get
applied by Vinod via linux-phy if possible. If you're not comfortable
with that please let me know and we'll try another solution.
I can bounce the patch to linux-ide. Should I also bounce the whole
series, or that patch only?
Marek
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2022-02-24 23:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 21:44 [PATCH phy v4 0/5] Armada 3720 comphy native implementation Marek Behún
2022-02-03 21:44 ` [PATCH phy v4 1/5] phy: marvell: phy-mvebu-a3700-comphy: Remove port from driver configuration Marek Behún
2022-02-03 21:44 ` [PATCH phy v4 2/5] phy: marvell: phy-mvebu-a3700-comphy: Add native kernel implementation Marek Behún
2022-02-03 21:44 ` [PATCH phy v4 3/5] Revert "ata: ahci: mvebu: Make SATA PHY optional for Armada 3720" Marek Behún
2022-02-24 15:13 ` Marek Behún
2022-02-24 15:14 ` Jens Axboe
2022-02-24 15:37 ` Marek Behún
2022-02-24 22:33 ` Damien Le Moal
2022-02-24 23:43 ` Marek Behún [this message]
2022-02-25 1:11 ` Damien Le Moal
2022-02-03 21:44 ` [PATCH phy v4 4/5] Revert "usb: host: xhci: mvebu: make USB 3.0 " Marek Behún
2022-02-24 15:12 ` Marek Behún
2022-02-25 10:50 ` Greg Kroah-Hartman
2022-02-03 21:44 ` [PATCH phy v4 5/5] Revert "PCI: aardvark: Fix initialization with old Marvell's Arm Trusted Firmware" Marek Behún
2022-02-25 13:43 ` [PATCH phy v4 0/5] Armada 3720 comphy native implementation Vinod Koul
2022-02-25 13:44 ` Pali Rohár
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=20220225004300.1bd1405e@thinkpad \
--to=kabel@kernel.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-phy@lists.infradead.org \
--cc=pali@kernel.org \
--cc=vkoul@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).