From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: linux-pci@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
bhelgaas@kernel.org, robh+dt@kernel.org, krzk@kernel.org,
jingoohan1@gmail.com, mark.rutland@arm.com, kgene@kernel.org
Subject: Re: [PATCH] PCI: exynos: remove the deprecated phy codes
Date: Wed, 3 Jan 2018 11:42:59 +0000 [thread overview]
Message-ID: <20180103114259.GA26554@red-moon> (raw)
In-Reply-To: <adf86cd6-ba78-33d5-284f-a31e0e9bf13c@samsung.com>
On Wed, Jan 03, 2018 at 02:26:29PM +0900, Jaehoon Chung wrote:
> On 01/03/2018 01:34 AM, Lorenzo Pieralisi wrote:
> > On Wed, Dec 27, 2017 at 06:43:27PM +0900, Jaehoon Chung wrote:
> >> pci-exynos had updated to use the PHY framework.
> >> (drivers/phy/samsung/phy-exynos-pcie.c)
> >> Removed the depreccated codes relevant to phy in pci-exynos.c.
> >> Instead, use the phy-exynos-pcie.c file.
> >>
> >> Modified the binding documentation.
> >>
> >> Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
> >> ---
> >> .../bindings/pci/samsung,exynos5440-pcie.txt | 58 ++----
> >> drivers/pci/dwc/pci-exynos.c | 219 ++-------------------
> >> 2 files changed, 22 insertions(+), 255 deletions(-)
> >
> > I have updated the commit log to the patch below, please
> > check before I push it out.
>
> Looks good to me. At next time, i will write the commit-msg more carefully.
No problem, applied to pci/dwc for v4.16, thanks.
Lorenzo
prev parent reply other threads:[~2018-01-03 11:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171227094329epcas1p2a7b0a0f6130db4361592d8966d5ecb85@epcas1p2.samsung.com>
2017-12-27 9:43 ` [PATCH] PCI: exynos: remove the deprecated phy codes Jaehoon Chung
2017-12-27 17:01 ` Jingoo Han
2017-12-27 17:01 ` Jingoo Han
2017-12-27 17:05 ` Jingoo Han
2017-12-27 17:05 ` Jingoo Han
2018-01-02 15:37 ` Rob Herring
2018-01-02 16:34 ` Lorenzo Pieralisi
2018-01-02 17:49 ` Jingoo Han
2018-01-02 17:49 ` Jingoo Han
2018-01-03 5:26 ` Jaehoon Chung
2018-01-03 11:42 ` Lorenzo Pieralisi [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=20180103114259.GA26554@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jh80.chung@samsung.com \
--cc=jingoohan1@gmail.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.