linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: 이왕석 <wangseok.lee@samsung.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"kishon@ti.com" <kishon@ti.com>,
	"vkoul@kernel.org" <vkoul@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"jesper.nilsson@axis.com" <jesper.nilsson@axis.com>,
	"lars.persson@axis.com" <lars.persson@axis.com>
Cc: "bhelgaas@google.com" <bhelgaas@google.com>,
	"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
	"kw@linux.com" <kw@linux.com>,
	"linux-arm-kernel@axis.com" <linux-arm-kernel@axis.com>,
	"kernel@axis.com" <kernel@axis.com>, 전문기 <moonki.jun@samsung.com>
Subject: Re: [PATCH 4/5] phy: Add ARTPEC-8 PCIe PHY driver
Date: Tue, 29 Mar 2022 15:22:20 +0900	[thread overview]
Message-ID: <20220329062220epcms2p2e66ed043478fd6c40906863cead7e8de@epcms2p2> (raw)
In-Reply-To: <da2351be-1fca-4269-cb7b-9dcd6a01b2dc@kernel.org>

> --------- Original Message ---------
> Sender : Krzysztof Kozlowski <krzk@kernel.org>
> Date : 2022-03-28 22:09 (GMT+9)
> Title : Re: [PATCH 4/5] phy: Add ARTPEC-8 PCIe PHY driver
>  
> On 28/03/2022 04:18, 이왕석 wrote:
>> Add support Axis, ARTPEC-8 SoC.
>> ARTPEC-8 is the SoC platform of Axis Communications.
>> This is based on arm64 and support GEN4 & 2lane.
>> This driver provides PHY interface for ARTPEC-8 SoC PCIe controller,
>> based on Samsung PCIe PHY IP.
>> 
> 
> You already sent it on 28th of January and did not respond to my comments.
> 
> Please do not resend same/similar code, but instead respond to comments
> received earlier.
> 
> Best regards,
> Krzysztof
Hello, Krzysztof

Yes, you are right.
I have sent a patch set this time, 
including parts that need to be modified in the previously sent patch.
Please ignore previously sent patch and refer to the new patch set.
I also replied to the previous e-mail,
but the email address was wrong and returned.

Thanks.

      parent reply	other threads:[~2022-03-29  6:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220328021832epcms2p6b6294b824c64404c437d0fd7f09369a4@epcms2p6>
2022-03-28  2:18 ` [PATCH 4/5] phy: Add ARTPEC-8 PCIe PHY driver 이왕석
2022-03-28 13:08   ` Krzysztof Kozlowski
     [not found]   ` <CGME20220328021832epcms2p6b6294b824c64404c437d0fd7f09369a4@epcms2p2>
2022-03-29  6:22     ` 이왕석 [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=20220329062220epcms2p2e66ed043478fd6c40906863cead7e8de@epcms2p2 \
    --to=wangseok.lee@samsung.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jesper.nilsson@axis.com \
    --cc=kernel@axis.com \
    --cc=kishon@ti.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kw@linux.com \
    --cc=lars.persson@axis.com \
    --cc=linux-arm-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=moonki.jun@samsung.com \
    --cc=robh+dt@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).