From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
rafael@kernel.org, robh+dt@kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH] dt-bindings: cpufreq: cpufreq-qcom-hw: Convert to YAML bindings
Date: Tue, 5 Oct 2021 10:21:51 +0530 [thread overview]
Message-ID: <20211005045151.GB4195@workstation> (raw)
In-Reply-To: <YVszd2UMw9F5LqWC@ripper>
On Mon, Oct 04, 2021 at 10:01:43AM -0700, Bjorn Andersson wrote:
> On Mon 04 Oct 00:22 PDT 2021, Manivannan Sadhasivam wrote:
>
> > On Mon, Oct 04, 2021 at 12:35:31PM +0530, Viresh Kumar wrote:
> > > On 04-10-21, 10:13, Manivannan Sadhasivam wrote:
> > > > Convert Qualcomm cpufreq devicetree binding to YAML.
> > > >
> > > > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> > > > Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
> > > > Reviewed-by: Rob Herring <robh@kernel.org>
> > >
> > > I am not sure if Rob ever gave this.
> > >
> >
> > I'm not fooling you :)
> > https://patchwork.kernel.org/project/linux-pm/patch/20210701105730.322718-5-angelogioacchino.delregno@somainline.org/#24312445
> >
> > > > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> > >
> > > Why double signed off ?
> > >
> >
> > Ah, it came while I applied the patch from Angelo's series. If you want
> > I can send a new version removing one or you can do that while applying.
> >
>
> If you wrote the patch, then Angelo handled it, then you handled it
> again the double S-o-b captures that nicely.
>
> Looking it from the other angle, if you remove the first S-o-b, then you
> forgot to signed it off when you authored the original patch and if you
> skip the last S-o-b then you didn't adequately sign off the final
> result.
>
Makes sense! I'll leave it as it is.
Thanks,
Mani
> Regards,
> Bjorn
>
> > Let me know.
> >
> > Thanks,
> > Mani
> >
> > > --
> > > viresh
next prev parent reply other threads:[~2021-10-05 4:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 4:43 [PATCH] dt-bindings: cpufreq: cpufreq-qcom-hw: Convert to YAML bindings Manivannan Sadhasivam
2021-10-04 7:05 ` Viresh Kumar
2021-10-04 7:22 ` Manivannan Sadhasivam
2021-10-04 8:59 ` Viresh Kumar
2021-10-04 9:03 ` Viresh Kumar
2021-10-04 12:54 ` Rob Herring
2021-10-04 17:01 ` Bjorn Andersson
2021-10-05 4:16 ` Viresh Kumar
2021-10-05 4:51 ` Manivannan Sadhasivam [this message]
2021-10-04 12:21 ` Rob Herring
2021-10-05 4:23 ` Viresh Kumar
2021-10-05 4:46 ` Manivannan Sadhasivam
2021-10-05 22:51 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2020-10-06 9:50 Manivannan Sadhasivam
2020-10-07 15:53 ` Rob Herring
2020-10-08 14:11 ` Manivannan Sadhasivam
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=20211005045151.GB4195@workstation \
--to=manivannan.sadhasivam@linaro.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=viresh.kumar@linaro.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 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).