From: Masahiro Yamada <masahiroy@kernel•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 kbuild tree
Date: Sat, 15 Mar 2025 21:24:51 +0900 [thread overview]
Message-ID: <CAK7LNAQWB__3BAfmJQYrXYsBa1D2=v355x12q4Rmoyro7LgiQw@mail.gmail.com> (raw)
In-Reply-To: <20250313002650.135e6383@canb.auug.org.au>
On Wed, Mar 12, 2025 at 10:26 PM Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Hi all,
>
> Commits
>
> bc5431693696 ("kbuild: exclude .rodata.(cst|str)* when building ranges")
> dafbec3f520b ("docs: kconfig: Mention IS_REACHABLE as way for optional dependency")
> 8ee44bd75bce ("scripts: make python shebangs specific about desired version")
> e6a2507c8d3c ("kbuild: rust: add rustc-min-version support function")
> 73d602eb38c3 ("gendwarfksyms: Add a separate pass to resolve FQNs")
>
> are missing a Signed-off-by from their committers.
Sorry, I made lots of mistakes.
Fixed now. Thanks.
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2025-03-15 12:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 13:26 linux-next: Signed-off-by missing for commit in the kbuild tree Stephen Rothwell
2025-03-15 12:24 ` Masahiro Yamada [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-16 11:26 Stephen Rothwell
2025-02-17 7:22 ` Stephen Rothwell
2024-09-17 20:41 Stephen Rothwell
2024-09-05 0:36 Stephen Rothwell
2022-11-29 21:08 Stephen Rothwell
2022-09-13 21:05 Stephen Rothwell
2022-04-06 6:45 Stephen Rothwell
2021-12-02 20:56 Stephen Rothwell
2021-02-24 3:46 Stephen Rothwell
2021-02-24 6:18 ` Masahiro Yamada
2020-01-13 19:45 Stephen Rothwell
2019-07-09 12:20 Stephen Rothwell
2019-07-09 13:36 ` Masahiro Yamada
2019-05-01 21:42 Stephen Rothwell
2019-05-03 10:37 ` Masahiro Yamada
2018-08-13 21:33 Stephen Rothwell
2018-08-14 2:47 ` Masahiro Yamada
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='CAK7LNAQWB__3BAfmJQYrXYsBa1D2=v355x12q4Rmoyro7LgiQw@mail.gmail.com' \
--to=masahiroy@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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