From: Namhyung Kim <namhyung@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Ian Rogers <irogers@google.com>,
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 perf-current tree
Date: Mon, 27 Jan 2025 15:56:17 -0800 [thread overview]
Message-ID: <Z5gdIQmCuHACmI-Z@google.com> (raw)
In-Reply-To: <20250128081222.0e16ae68@canb.auug.org.au>
On Tue, Jan 28, 2025 at 08:12:22AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 191f1bd6492a ("perf annotate: Use an array for the disassembler preference")
>
> is missing a Signed-off-by from its author.
>
> Looks like the SoB was after the '--' separator in the original emailed
> patch.
Oops, sorry I missed that. I'll force push with SoB soon.
Thanks,
Namhyung
prev parent reply other threads:[~2025-01-27 23:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 21:12 linux-next: Signed-off-by missing for commit in the perf-current tree Stephen Rothwell
2025-01-27 23:56 ` Namhyung Kim [this message]
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=Z5gdIQmCuHACmI-Z@google.com \
--to=namhyung@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=irogers@google.com \
--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