From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Juergen Gross <jgross@suse.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"kernelci.org bot" <bot@kernelci.org>
Subject: Re: linux-next: build failure after merge of the mm-hotfixes tree
Date: Fri, 25 Nov 2022 16:48:57 +1100 [thread overview]
Message-ID: <20221125164857.25b63a58@canb.auug.org.au> (raw)
In-Reply-To: <20221124212457.06a9928d931d00ad98d7d454@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
Hi Andrew,
On Thu, 24 Nov 2022 21:24:57 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Fri, 25 Nov 2022 12:10:51 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Hi all,
> >
> > After merging the mm-hotfixes tree, today's linux-next build (arm
> > allmodconfig) failed like this:
> >
> > mm/vmscan.c:4090:9: error: implicit declaration of function ‘pmd_young’; did you mean ‘pte_young’? [-Werror=implicit-function-declaration]
> >
> > Caused by commit
> >
> > 3f85e711d5af ("mm: introduce arch_has_hw_nonleaf_pmd_young()")
> >
> > This error was found by the kernel.ci bot and so is still int today's
> > tree.
>
> Thanks. Did that tree include "mm: add dummy pmd_young() for
> architectures not having it"?
It did not when I merged the mm-hotfixes branch, but then I refetched
your trees during the day and so that patch appeared when I merged the
mm tree (which is now based on a later version of the mm-hotfixes
branch). So next-20221125 as a whole will not have the build failure.
After I merge all the "fixes" branches, I upload a "pending-updates"
branch that feeds into the various bots independently of the full next
tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-11-25 5:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 1:10 linux-next: build failure after merge of the mm-hotfixes tree Stephen Rothwell
2022-11-25 5:24 ` Juergen Gross
2022-11-25 5:24 ` Andrew Morton
2022-11-25 5:48 ` Stephen Rothwell [this message]
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
2023-12-13 22:18 Stephen Rothwell
2023-12-13 23:31 ` Liam R. Howlett
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=20221125164857.25b63a58@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=bot@kernelci.org \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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 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).