All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "Rob Herring" <robh@kernel.org>
Cc: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"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: Wed, 28 Jun 2023 08:49:56 +0200	[thread overview]
Message-ID: <CTO30OAFFNFB.18YWUN5KFZVTA@otso> (raw)
In-Reply-To: <20230627151842.GB1918927-robh@kernel.org>

On Tue Jun 27, 2023 at 5:18 PM CEST, Rob Herring wrote:
> On Mon, Jun 26, 2023 at 10:19:09AM +0200, Luca Weiss wrote:
> > 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.
>
> I just put a '---' line and comments after that in the commit messages. 
> That works fine unless your git branch is going upstream directly (i.e. 
> via a pull request). Even when I apply my own patches, I get them from 
> lore and apply so the comments are dropped.

Ah, didn't know this was possible/supported. In the past with git
send-email directly I'd edit the patch file and add some text under the
"---" manually but wasn't aware you can put it directly in the commit
message. But I guess if it produces the same output either way it makes
sense.

I won't have a problem with pull requests since I'm just a normal patch
submitter ;)

Thanks for the advice!

Regards
Luca

>
> Rob


  reply	other threads:[~2023-06-28  8:06 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
2023-06-27 15:18               ` Rob Herring
2023-06-28  6:49                 ` Luca Weiss [this message]
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=CTO30OAFFNFB.18YWUN5KFZVTA@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.