linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Willy Tarreau <w@1wt.eu>,
	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 rcu tree
Date: Fri, 9 Jun 2023 12:00:36 -0700	[thread overview]
Message-ID: <5db31cea-470f-453b-ae1f-28c67a2128e5@paulmck-laptop> (raw)
In-Reply-To: <20230609083102.0a063bc0@canb.auug.org.au>

On Fri, Jun 09, 2023 at 08:31:02AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
>   bc6edad600e6 ("selftests/nolibc: make sure gcc always use little endian on MIPS")
>   15f57edf4753 ("selftests/nolibc: also count skipped and failed tests in output")
>   87c76b30c631 ("selftests/nolibc: add new gettimeofday test cases")
>   168bacf2b889 ("selftests/nolibc: remove gettimeofday_bad1/2 completely")
>   b58a501ed987 ("selftests/nolibc: support two errnos with EXPECT_SYSER2()")
>   5b654b2c0284 ("tools/nolibc: open: fix up compile warning for arm")
>   a50316875429 ("tools/nolibc: arm: add missing my_syscall6")
>   1993d9c770c2 ("selftests/nolibc: use INT_MAX instead of __INT_MAX__")
>   fc41c241d79c ("selftests/nolibc: not include limits.h for nolibc")
>   a8b20e76e877 ("selftests/nolibc: fix up compile warning with glibc on x86_64")
>   d785d831bde5 ("selftests/nolibc: allow specify extra arguments for qemu")
>   df772c12508a ("selftests/nolibc: syscall_args: use generic __NR_statx")
>   3f83dcdf4fc6 ("selftests/nolibc: remove test gettimeofday_null")
>   a54457590ece ("tools/nolibc: ensure fast64 integer types have 64 bits")
>   a232f7f31314 ("selftests/nolibc: test_fork: fix up duplicated print")
>   c79ff8143435 ("tools/nolibc: ppoll/ppoll_time64: add a missing argument")
>   b1f9a5df6b53 ("selftests/nolibc: remove the duplicated gettimeofday_bad2")
>   b38d446d8364 ("selftests/nolibc: print name instead of number for EOVERFLOW")
>   37363156afc3 ("tools/nolibc: support nanoseconds in stat()")
>   6a1935f83840 ("selftests/nolibc: prevent coredumps during test execution")
>   6066aced432c ("tools/nolibc: add support for prctl()")
>   997c1685b7ec ("tools/nolibc: s390: disable stackprotector in _start")
>   4eb9ada569ee ("tools/nolibc: fix segfaults on compilers without attribute no_stack_protector")
>   be5547775590 ("tools/nolibc: simplify stackprotector compiler flags")
>   ea22ffdf3acf ("tools/nolibc: add autodetection for stackprotector support")
>   92b85d2cc2e4 ("tools/nolibc: reformat list of headers to be installed")
>   af29d2e6df83 ("tools/nolibc: add test for __stack_chk_guard initialization")
>   b0e9a86caded ("tools/nolibc: ensure stack protector guard is never zero")
>   f14f35a85ee6 ("tools/nolibc: x86_64: disable stack protector for _start")
>   9d15cbe52c62 ("tools/nolibc: fix typo pint -> point")
>   340529052f74 ("tools/nolibc: riscv: add stackprotector support")
>   9b80e2f60acb ("tools/nolibc: mips: add stackprotector support")
>   58ac7b1823c7 ("tools/nolibc: loongarch: add stackprotector support")
>   3259f396c0e6 ("tools/nolibc: arm: add stackprotector support")
>   8411f6ee8393 ("tools/nolibc: aarch64: add stackprotector support")
>   8c9ea6b3d1b7 ("selftests/nolibc: reduce syscalls during space padding")
>   6bff2a1e97e3 ("tools/nolibc/unistd: add syscall()")
>   5f97e9feb11e ("tools/nolibc: riscv: Fix up load/store instructions for rv32")
> 
> are missing a Signed-off-by from their committer.
> 
> It looks like you should have merged someone else's branch, but ended
> up rebasing it instead.

We will be moving to me pulling directly from Willy's tree, but that will
be next cycle.  Me, I stupidly forgot the "-s" argument.  Apologies for
the hassle, and fixed.

							Thanx, Paul

  reply	other threads:[~2023-06-09 19:00 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 22:31 linux-next: Signed-off-by missing for commit in the rcu tree Stephen Rothwell
2023-06-09 19:00 ` Paul E. McKenney [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-07 20:39 Stephen Rothwell
2024-02-08 16:07 ` Paul E. McKenney
2023-06-08 22:27 Stephen Rothwell
2023-06-08 22:28 ` Stephen Rothwell
2023-06-09  4:08   ` Zhangjin Wu
2023-06-09  9:24     ` Willy Tarreau
2023-05-16 22:41 Stephen Rothwell
2023-05-16 22:54 ` Paul E. McKenney
2023-03-08  2:16 Stephen Rothwell
2023-03-08 17:41 ` Paul E. McKenney
2022-09-22 10:12 Stephen Rothwell
2022-09-22 13:55 ` Paul E. McKenney
2022-01-03 21:38 Stephen Rothwell
2022-01-03 23:33 ` Paul E. McKenney
2021-05-23  3:02 Stephen Rothwell
2021-05-24  3:49 ` Paul E. McKenney
2021-03-08  6:03 Stephen Rothwell
2021-03-09  5:24 ` Paul E. McKenney
2021-01-10  2:24 Stephen Rothwell
2021-01-10  5:15 ` Paul E. McKenney
2020-11-22 10:08 Stephen Rothwell
2020-11-22 10:09 ` Stephen Rothwell
2020-11-22 17:51   ` Paul E. McKenney
2020-09-29 22:37 Stephen Rothwell
2020-09-30  4:43 ` Paul E. McKenney
2020-09-17  3:26 Stephen Rothwell
2020-09-17 18:00 ` Paul E. McKenney
2020-09-22 22:35   ` Stephen Rothwell
2020-09-28  7:57   ` Peter Zijlstra
2020-09-28 17:33     ` Paul E. McKenney
2020-11-18 23:40       ` Paul E. McKenney
2020-02-12 22:25 Stephen Rothwell
2020-02-13 21:38 ` Joel Fernandes
2020-02-27 15:10   ` Paul E. McKenney
2019-10-28 20:53 Stephen Rothwell
2019-10-29  0:37 ` Paul E. McKenney
2018-04-23 21:48 Stephen Rothwell
2018-04-23 22:16 ` Paul E. McKenney
2018-02-26 22:38 Stephen Rothwell
2018-02-26 23:22 ` Paul E. McKenney
2017-11-29  0:51 Stephen Rothwell
2017-11-29  1:14 ` Paul E. McKenney
2017-11-29  2:48   ` Lihao Liang
2017-11-29  3:14     ` Hanjun Guo
2017-11-29  3:29       ` Lihao Liang
2017-11-29 20:54         ` Paul E. McKenney
2017-07-30 13:48 Stephen Rothwell
2017-07-30 16:57 ` Paul E. McKenney

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=5db31cea-470f-453b-ae1f-28c67a2128e5@paulmck-laptop \
    --to=paulmck@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=w@1wt.eu \
    /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).