From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Qiang Zhang <qiang4.zhang@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the mm-hotfixes tree
Date: Wed, 17 Apr 2024 13:53:02 -0700 [thread overview]
Message-ID: <20240417135302.2f5c6a9ab9eb2ef58e1bdc7b@linux-foundation.org> (raw)
In-Reply-To: <20240417152904.17fa874d@canb.auug.org.au>
On Wed, 17 Apr 2024 15:29:04 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > * This clears all data structures of parsed bootconfig on memory.
> > * If you need to reuse xbc_init() with new boot config, you can
> > _
> >
>
> OK, so the above two warnings went away, but now I get
>
> lib/bootconfig.c:909: warning: expecting prototype for _xbc_exit(). Prototype was for xbc_exit() instead
>
> Commit
>
> aaeda6237dec ("bootconfig: use memblock_free_late to free xbc memory to buddy")
>
> that was in the mm tree yesterday is not there now.
oop, sorry, fat-fingered that one. Thanks, I brought back
bootconfig-use-memblock_free_late-to-free-xbc-memory-to-buddy.patch.
next prev parent reply other threads:[~2024-04-17 20:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 7:35 linux-next: build warning after merge of the mm-hotfixes tree Stephen Rothwell
2024-04-16 18:51 ` Andrew Morton
2024-04-17 5:29 ` Stephen Rothwell
2024-04-17 20:53 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-25 3:55 Stephen Rothwell
2023-07-25 4:10 ` Hugh Dickins
2023-07-25 5:16 ` Randy Dunlap
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=20240417135302.2f5c6a9ab9eb2ef58e1bdc7b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=qiang4.zhang@intel.com \
--cc=sfr@canb.auug.org.au \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).