From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Ruffalo Lavoisier <ruffalolavoisier@gmail.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 tree
Date: Mon, 16 Dec 2024 21:33:39 -0300 [thread overview]
Message-ID: <Z2DG41WOlZgQl9Ue@x1> (raw)
In-Reply-To: <20241216082725.2ef47ce1@canb.auug.org.au>
On Mon, Dec 16, 2024 at 08:27:25AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 8791a78fb70e ("perf test: Remove duplicate word")
>
> is missing a Signed-off-by from its author.
>
> This is probably not necessarily necessary ;-)
:-)
I can force push after the original author provides the Signed-off-by,
but for such a simple patch can we just keep things as-is?
Is that that what you're saying?
- Arnaldo
next prev parent reply other threads:[~2024-12-17 0:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 21:27 linux-next: Signed-off-by missing for commit in the perf tree Stephen Rothwell
2024-12-17 0:33 ` Arnaldo Carvalho de Melo [this message]
2024-12-17 0:39 ` Stephen Rothwell
2024-12-17 0:55 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2025-12-04 22:24 Stephen Rothwell
2025-12-04 22:52 ` Ian Rogers
2025-12-04 23:41 ` Namhyung Kim
2023-12-05 22:14 Stephen Rothwell
2023-12-06 12:33 ` Arnaldo Carvalho de Melo
2023-09-14 21:26 Stephen Rothwell
2023-09-15 2:50 ` Namhyung Kim
2022-12-13 21:34 Stephen Rothwell
2022-12-13 21:36 ` Arnaldo Carvalho de Melo
2022-12-13 21:40 ` Ian Rogers
2022-10-30 20:45 Stephen Rothwell
2022-10-31 14:04 ` Arnaldo Carvalho de Melo
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=Z2DG41WOlZgQl9Ue@x1 \
--to=acme@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=ruffalolavoisier@gmail.com \
--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 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.