From: Vinod Koul <vkoul@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Jaehoon Chung <jh80.chung@samsung.com>,
Jingoo Han <jingoohan1@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Rob Herring <robh@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH v4 4/5] phy: samsung: phy-exynos-pcie: rework driver to support Exynos5433 PCIe PHY
Date: Fri, 20 Nov 2020 15:41:38 +0530 [thread overview]
Message-ID: <20201120101138.GI2925@vkoul-mobl> (raw)
In-Reply-To: <8eaebd62-345f-4d13-1b65-055a2acc68bd@samsung.com>
On 20-11-20, 10:58, Marek Szyprowski wrote:
> Hi Vinod,
>
> On 20.11.2020 10:41, Vinod Koul wrote:
> > On 13-11-20, 18:01, Marek Szyprowski wrote:
> >> From: Jaehoon Chung <jh80.chung@samsung.com>
> >>
> >> Exynos5440 SoC support has been dropped since commit 8c83315da1cf ("ARM:
> >> dts: exynos: Remove Exynos5440"). Rework this driver to support PCIe PHY
> >> variant found in the Exynos5433 SoCs.
> > I am expecting this series to go thru PCI tree, so:
> >
> > Acked-By: Vinod Koul <vkoul@kernel.org>
>
> Frankly, the PHY driver can also go via PHY tree without causing any
> issue. The old driver is not used at all, so there is no runtime
> dependency. This will help avoiding the merge conflict: yesterday I've
> noticed that this patch conflicts with the commit 2f0c9fac3be6 ("phy:
> samsung: convert to devm_platform_ioremap_resource") in phy-next. The
> resolution is simple (use all the code from the new driver), but if
> needed I can resend the PHY driver after a rebase onto the current next
> tree.
Okay do send me the rebase patch
Thanks
--
~Vinod
next prev parent reply other threads:[~2020-11-20 10:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201113170156eucas1p176314e4076c593d1f2e68159be880f86@eucas1p1.samsung.com>
2020-11-13 17:01 ` [PATCH v4 0/5] Add DW PCIe support for Exynos5433 SoCs Marek Szyprowski
2020-11-13 17:01 ` [PATCH v4 1/5] dt-bindings: PCI: exynos: drop samsung,exynos5440-pcie binding Marek Szyprowski
2020-11-13 17:01 ` [PATCH v4 2/5] dt-bindings: PCI: exynos: add the samsung,exynos-pcie binding Marek Szyprowski
2020-11-13 17:01 ` [PATCH v4 3/5] dt-bindings: phy: exynos: add the samsung,exynos-pcie-phy binding Marek Szyprowski
2020-11-13 17:01 ` [PATCH v4 4/5] phy: samsung: phy-exynos-pcie: rework driver to support Exynos5433 PCIe PHY Marek Szyprowski
2020-11-20 9:41 ` Vinod Koul
2020-11-20 9:58 ` Marek Szyprowski
2020-11-20 10:11 ` Vinod Koul [this message]
2020-11-20 10:26 ` [PATCH v4 4/5 REBASED RESEND] " Marek Szyprowski
2020-11-20 10:36 ` Vinod Koul
2020-11-13 17:01 ` [PATCH v4 5/5] PCI: dwc: exynos: Rework the driver to support Exynos5433 variant Marek Szyprowski
2020-11-23 9:53 ` [PATCH v4 0/5] Add DW PCIe support for Exynos5433 SoCs Lorenzo Pieralisi
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=20201120101138.GI2925@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=jh80.chung@samsung.com \
--cc=jingoohan1@gmail.com \
--cc=kishon@ti.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=m.szyprowski@samsung.com \
--cc=robh@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).