From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Stanislav Jakubek <stano.jakubek@gmail.com>
Cc: agross@kernel.org, devicetree@vger.kernel.org,
linus.walleij@linaro.org, linux-arm-msm@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
manivannan.sadhasivam@linaro.org, olof@lixom.net,
quic_vamslank@quicinc.com, robh+dt@kernel.org,
sboyd@codeaurora.org, soc@kernel.org
Subject: Re: [PATCH v3 0/3] Add devicetree support for SDX65 Modem and MTP
Date: Thu, 23 Dec 2021 07:45:11 -0800 [thread overview]
Message-ID: <YcSZh8racQsDiF5O@ripper> (raw)
In-Reply-To: <20211223144407.GA6503@standask-GA-A55M-S2HP>
On Thu 23 Dec 06:44 PST 2021, Stanislav Jakubek wrote:
> Hi Bjorn, it seems to me like a patch similar to Patch 1/3 was applied
> some time ago, see 61339f368d59d25e22401731f89de44e3215508b, and applying
> this patch has caused the compatible to be documented twice.
>
I'm confused to why git allowed me to merge patch 1 without complaining,
but that obviously shouldn't have been merged twice. Thanks for
reporting this!
Let's clean that up, would you be interested in submitting a patch for
it?
Regards,
Bjorn
prev parent reply other threads:[~2021-12-23 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 0:02 [PATCH v3 0/3] Add devicetree support for SDX65 Modem and MTP quic_vamslank
2021-10-30 0:02 ` [PATCH v3 1/3] dt-bindings: arm: qcom: Document SDX65 platform and boards quic_vamslank
2021-10-30 0:02 ` [PATCH v3 2/3] ARM: dts: qcom: Add SDX65 platform and MTP board support quic_vamslank
2021-10-30 0:02 ` [PATCH v3 3/3] ARM: dts: qcom: sdx65: Add pincontrol node quic_vamslank
2021-12-02 0:34 ` [PATCH v3 0/3] Add devicetree support for SDX65 Modem and MTP Vamsi Krishna Lanka
2021-12-15 22:27 ` Bjorn Andersson
2021-12-23 14:44 ` Stanislav Jakubek
2021-12-23 15:45 ` Bjorn Andersson [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=YcSZh8racQsDiF5O@ripper \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=olof@lixom.net \
--cc=quic_vamslank@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=soc@kernel.org \
--cc=stano.jakubek@gmail.com \
/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.