linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	<linux-arm-msm@vger.kernel.org>,
	"Bjorn Andersson" <bjorn.andersson@linaro.org>
Cc: <~postmarketos/upstreaming@lists.sr.ht>,
	<phone-devel@vger.kernel.org>, "Rob Herring" <robh@kernel.org>,
	"Andy Gross" <agross@kernel.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Marc Zyngier" <maz@kernel.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: qcom,pdc: convert to YAML
Date: Mon, 16 May 2022 09:45:20 +0200	[thread overview]
Message-ID: <CK10OTVFAP75.WCSVY40A7PXO@otso> (raw)
In-Reply-To: <fef5f229-f247-d032-fc76-46ed7083dbf4@linaro.org>

Hi Krzysztof,

On Mon May 9, 2022 at 10:40 AM CEST, Krzysztof Kozlowski wrote:
> On 09/05/2022 10:38, Krzysztof Kozlowski wrote:
> > On 03/01/2022 08:43, Luca Weiss wrote:
> >> Convert the PDC interrupt controller bindings to YAML.
> >>
> >> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
> >> Reviewed-by: Rob Herring <robh@kernel.org>
> >> ---
> >> Changes since v1:
> >> * Adjust description of second reg-name as suggested by Maulik Shah
> >>
> >> @Rob Herring: Hope it's ok to keep your R-b given the above changes
> >>
> >> This patch depends on the following patch, which fixed sm8250 & sm8350
> >> compatibles and adds sm6350.
> >> https://lore.kernel.org/linux-arm-msm/20211213082614.22651-4-luca.weiss@fairphone.com/
> > 
> > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > 
> > Luca,
> > I think this needs resending as dependency was merged. Alternatively,
> > maybe Bjorn could pick it up through QCom SoC?
>
> Correction - it seems that Rob took the dependency in April, so this
> should go via Rob's tree as well.
>
> Luca, can you resend without Rob's Review tag and ask him to pick it up?
>

So... since torvalds/master my sm6350 patch is merged through Rob's
tree, but there was also a sm8150 patch applied through Linus Walleij's
tree. This means (as far as I understand) that neither can really
properly apply this (rebased) patch as one tree will have missed the
other commit.

Does it make sense to send a v3 rebased on linux-next now, or wait until
this has settled down in torvalds's tree?

Regards
Luca

>
> Best regards,
> Krzysztof


  reply	other threads:[~2022-05-16  7:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03  7:43 [PATCH v2] dt-bindings: qcom,pdc: convert to YAML Luca Weiss
2022-05-09  8:38 ` Krzysztof Kozlowski
2022-05-09  8:40   ` Krzysztof Kozlowski
2022-05-16  7:45     ` Luca Weiss [this message]
2022-05-16 10:35       ` Krzysztof Kozlowski
2022-05-16 11:22         ` Luca Weiss
2022-09-09 14:39 ` Rob Herring
2022-09-12  6:50   ` Luca Weiss

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=CK10OTVFAP75.WCSVY40A7PXO@otso \
    --to=luca.weiss@fairphone.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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).