From: "Liam R. Howlett" <Liam.Howlett@Oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Sidhartha Kumar <sidhartha.kumar@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>
Subject: Re: linux-next: build failure after merge of the mm-hotfixes tree
Date: Wed, 13 Dec 2023 18:31:28 -0500 [thread overview]
Message-ID: <20231213233128.vsg3ktm7num3re4r@revolver> (raw)
In-Reply-To: <20231214091831.70cc51e0@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> [231213 17:18]:
> Hi all,
>
> After merging the mm-hotfixes tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> lib/maple_tree.c: In function 'mas_preallocate':
> lib/maple_tree.c:5506:30: error: 'struct ma_state' has no member named 'end'
> 5506 | if ((node_size == mas->end) && ((!mt_in_rcu(mas->tree))
> | ^~
>
> Caused by commit
>
> 84bda0b24555 ("maple_tree: do not preallocate nodes for slot stores")
>
> I have reverted that commit for today.
No harm in leaving it, but akpm made a 'fixlet' for this [1]. The word
fixlet made my day. I assume this will be fix(let)ed tomorrow.
Cheers,
Liam
[1] https://lore.kernel.org/linux-mm/20231213130923.cc00317b4ebab1b0864d8b42@linux-foundation.org/
next prev parent reply other threads:[~2023-12-13 23:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 22:18 linux-next: build failure after merge of the mm-hotfixes tree Stephen Rothwell
2023-12-13 23:31 ` Liam R. Howlett [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-12 22:30 Stephen Rothwell
2022-12-13 1:34 ` Kefeng Wang
2022-12-13 2:23 ` Andrew Morton
2022-12-13 2:45 ` Stephen Rothwell
2022-12-13 2:54 ` Kefeng Wang
2022-11-25 1:10 Stephen Rothwell
2022-11-25 5:24 ` Juergen Gross
2022-11-25 5:24 ` Andrew Morton
2022-11-25 5:48 ` 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=20231213233128.vsg3ktm7num3re4r@revolver \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sidhartha.kumar@oracle.com \
--cc=willy@infradead.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 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).