From: Viresh Kumar <viresh.kumar@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the cpufreq-arm tree
Date: Fri, 26 Apr 2024 18:16:27 +0530 [thread overview]
Message-ID: <20240426124627.nscubryyy77pp4nz@vireshk-i7> (raw)
In-Reply-To: <20240426065343.4a29617b@canb.auug.org.au>
On 26-04-24, 06:53, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 51090b2ef6ea ("dt-bindings: cpufreq: cpufreq-qcom-hw: Add SM4450 compatibles")
>
> is missing a Signed-off-by from its committer.
Sorry about that. Fixed now.
--
viresh
next prev parent reply other threads:[~2024-04-26 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 20:53 linux-next: Signed-off-by missing for commit in the cpufreq-arm tree Stephen Rothwell
2024-04-26 12:46 ` Viresh Kumar [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-11 3:21 Stephen Rothwell
2019-12-11 5:06 ` Viresh Kumar
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=20240426124627.nscubryyy77pp4nz@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).