From: Mike Rapoport <rppt@kernel.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Song Hu <husong@kylinos.cn>,
linux-mm@kvack.org, muchun.song@linux.dev, osalvador@suse.de,
ljs@kernel.org, liam@infradead.org, vbabka@kernel.org,
surenb@google.com, mhocko@suse.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Mina Almasry <almasrymina@google.com>
Subject: Re: [PATCH 2/2] selftests/mm: restore hidden hugetlb reservation scenarios
Date: Sun, 6 Sep 2026 11:28:07 +0300 [thread overview]
Message-ID: <ap0kF3dWU8UWaCpO@kernel.org> (raw)
In-Reply-To: <929d0143-91c5-4b47-8e38-30675b4ace5d@kernel.org>
On Sat, Sep 05, 2026 at 10:17:12AM +0200, David Hildenbrand (Arm) wrote:
> On 9/4/26 19:48, Andrew Morton wrote:
> > On Fri, 4 Sep 2026 11:30:23 +0300 Mike Rapoport <rppt@kernel.org> wrote:
> >
> >> On Tue, Sep 01, 2026 at 05:37:48PM -0700, Andrew Morton wrote:
> >>>
> >>>
> >>> OK.
> >>>
> >>>
> >>> That's reasonable. This code was added by Mina six years ago. But
> >>> he's still around so let's bug him with a cc ;)
> >>
> >> And this code breaks our CI e.g:
> >>
> >> https://github.com/linux-mm/linux-mm/actions/runs/33040981840/job/98414290236
> >
> > What do we need to do to view the error output there?
>
> I recall that one has to be logged in in github in order to view the output:
>
> @Mike once sending automated CI failure mails, would it be possible to include
> the full output?
I'll take a look.
> --
> Cheers,
>
> David
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2026-09-06 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 2:16 [PATCH 2/2] selftests/mm: restore hidden hugetlb reservation scenarios Song Hu
2026-09-02 0:37 ` Andrew Morton
2026-09-04 8:30 ` Mike Rapoport
2026-09-04 17:48 ` Andrew Morton
2026-09-05 8:17 ` David Hildenbrand (Arm)
2026-09-06 8:28 ` Mike Rapoport [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=ap0kF3dWU8UWaCpO@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=almasrymina@google.com \
--cc=david@kernel.org \
--cc=husong@kylinos.cn \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
/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.