All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mars Chen <chenxiangrui@huaqin.corp-partner.google.com>,
	Matthias Kaehlcke <mka@chromium.org>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: Add sc7180-gelarshie
Date: Thu, 7 Apr 2022 13:46:19 +0200	[thread overview]
Message-ID: <47f0c906-02be-2635-15e9-4ad8866a3a62@kernel.org> (raw)
In-Reply-To: <78ddc1a6-4597-46b7-76f0-32087ed62546@kernel.org>

On 07/04/2022 13:38, Krzysztof Kozlowski wrote:
> On 07/04/2022 10:15, Mars Chen wrote:
>> Hi Matthias,
>> I had removed camera related files on upstream device trees.
>>
>> Hi Krzysztof,
>> The v2 patch just addressed the v1 patch comment and I had sent the v2
>> patch. 
>>
> 
> Hi,
> 
> I do not see it being addressed at all. :(

What is more, this is your third try and still did not fix the
checkpatch warning (which is the same issue I pointed out). Did you run
the checkpatch before sending the patch?

Best regards,
Krzysztof

  reply	other threads:[~2022-04-07 11:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  9:41 [PATCH] arm64: dts: qcom: Add sc7180-gelarshie Mars Chen
2022-04-06 14:38 ` Krzysztof Kozlowski
2022-04-06 15:43 ` Matthias Kaehlcke
     [not found]   ` <CA+Bnokw-8023cvifSZtT8WR4TvUi8K3512TmEoXhKezMjbQNUQ@mail.gmail.com>
2022-04-07 11:38     ` Krzysztof Kozlowski
2022-04-07 11:46       ` Krzysztof Kozlowski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-06  7:47 Mars Chen
2022-04-06  7:37 Mars Chen

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=47f0c906-02be-2635-15e9-4ad8866a3a62@kernel.org \
    --to=krzk@kernel.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=chenxiangrui@huaqin.corp-partner.google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mka@chromium.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 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.