From: Andrew Morton <akpm@linux-foundation•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Li Wang <liwang@redhat•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 mm-unstable tree
Date: Sun, 4 Jan 2026 17:26:22 -0800 [thread overview]
Message-ID: <20260104172622.ab628adfd6056401b68b2011@linux-foundation.org> (raw)
In-Reply-To: <20260105083851.19677121@canb.auug.org.au>
On Mon, 5 Jan 2026 08:38:51 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Commits
>
> 8bd5f5187a2f ("selftests/mm/charge_reserved_hugetlb.sh: add waits with timeout helper")
> 378d74dfdea6 ("selftests/mm/charge_reserved_hugetlb: drop mount size for hugetlbfs")
> 99f5e30c38ac ("selftests/mm/write_to_hugetlbfs: parse -s as size_t")
huh, thanks. The changelogs have
: The hugetlb cgroup usage wait loops in charge_reserved_hugetlb.sh were
: unbounded and could hang forever if the expected cgroup file value never
: appears (e.g. due to write_to_hugetlbfs in Error mapping).
:
: --- Error log ---
and that "^---$" fooled git-quiltimport into thinking "end of
changelog". Huh.
I'll fix that and shall figure out some way to check for reoccurrences.
next prev parent reply other threads:[~2026-01-05 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 21:38 linux-next: Signed-off-by missing for commit in the mm-unstable tree Stephen Rothwell
2026-01-05 1:26 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-12 5:55 Stephen Rothwell
2025-04-15 6:57 Stephen Rothwell
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=20260104172622.ab628adfd6056401b68b2011@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=liwang@redhat$(echo .)com \
--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