From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Rob Herring" <robh@kernel.org>
Cc: "Abel Vesa" <abel.vesa@linaro.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Andy Gross" <agross@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konrad.dybcio@linaro.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Avri Altman" <avri.altman@wdc.com>,
"Bart Van Assche" <bvanassche@acm.org>,
<linux-arm-msm@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
<devicetree@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/5] scsi: dt-bindings: ufs: qcom: Fix warning for sdm845 by adding reg-names
Date: Mon, 26 Jun 2023 10:19:09 +0200 [thread overview]
Message-ID: <CTMFNWKMSCJP.DBPZEW25594L@otso> (raw)
In-Reply-To: <d3970163-b8e8-9665-3761-8942c28adaa8@linaro.org>
On Mon Jun 26, 2023 at 9:41 AM CEST, Krzysztof Kozlowski wrote:
> On 26/06/2023 08:38, Luca Weiss wrote:
> >>>> but I guess no resends and it can be superseded.
> >>>
> >>> Right, the patches got reviews but was never applied... I really need to
> >>> find a strategy to keep track of sent patches until they're applied with
> >>> my work mailbox, it's not the first time that a patch has gotten
> >>> forgotten.
> >>
> >> There was an error reported on the above series. Why would it be
> >> applied?
> >
> > The error report at [0] complains about reg-names but I'm quite sure
> > that patch 2/3 resolves this error. Does your bot only apply one patch
> > at a time and run the check or apply all of them and then run it? It's
> > been a while but I'm fairly sure I ran all of the checks before sending
> > since I also documented some other patches in the cover letter there.
>
> You did it in cover letter, not in the patch, so there is no dependency
> for bots recorded.
I'm not aware how to put extra comments into a patch in a series with
b4, at least last time I checked I don't think it was possible? But I
also thought the cover letter was exactly there for giving some
background of the series and documenting any dependencies on other
patches.
>
> >
> > [0] https://lore.kernel.org/all/167241769341.1925758.17856681634949446114.robh@kernel.org/
>
> Your patch 2/3 could not be applied to any tree. 3/3 applied but without
> previous one caused warnings.
Anyways, just resent the series as v4, maybe this time it can get picked
up... Should have enough reviews by now :)
Regards
Luca
>
>
>
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2023-06-26 8:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 11:30 [PATCH 0/5] scsi: dt-bindings: ufs: qcom: Some fixes to clear all dtbs_check warnings Abel Vesa
2023-06-23 11:30 ` [PATCH 1/5] scsi: dt-bindings: ufs: qcom: Fix ICE phandle Abel Vesa
2023-06-23 16:45 ` Krzysztof Kozlowski
2023-06-23 11:30 ` [PATCH 2/5] scsi: dt-bindings: ufs: qcom: Add compatible for sm6115 and sm6125 Abel Vesa
2023-06-23 12:33 ` Krzysztof Kozlowski
2023-06-23 12:34 ` Krzysztof Kozlowski
2023-06-23 11:30 ` [PATCH 3/5] scsi: dt-bindings: ufs: qcom: Add compatible for sc8180x Abel Vesa
2023-06-23 12:30 ` Krzysztof Kozlowski
2023-06-23 11:30 ` [PATCH 4/5] scsi: dt-bindings: ufs: qcom: Fix sm8450 clocks Abel Vesa
2023-06-23 12:21 ` Rob Herring
2023-06-23 20:12 ` Rob Herring
2023-06-23 11:30 ` [PATCH 5/5] scsi: dt-bindings: ufs: qcom: Fix warning for sdm845 by adding reg-names Abel Vesa
2023-06-23 12:31 ` Krzysztof Kozlowski
2023-06-23 12:38 ` Luca Weiss
2023-06-23 21:17 ` Rob Herring
2023-06-24 7:49 ` Krzysztof Kozlowski
2023-06-27 15:14 ` Rob Herring
2023-06-26 6:38 ` Luca Weiss
2023-06-26 7:41 ` Krzysztof Kozlowski
2023-06-26 8:19 ` Luca Weiss [this message]
2023-06-27 15:18 ` Rob Herring
2023-06-28 6:49 ` Luca Weiss
2023-06-24 12:30 ` James Bottomley
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=CTMFNWKMSCJP.DBPZEW25594L@otso \
--to=luca.weiss@fairphone.com \
--cc=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andersson@kernel.org \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=robh@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.