Linux-Next Archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
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: linux-next: build warning after merge of the mm-hotfixes tree
Date: Tue, 16 Apr 2024 17:35:25 +1000	[thread overview]
Message-ID: <20240416173525.13bfd8dc@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 529 bytes --]

Hi all,

After merging the mm-hotfixes tree, today's linux-next build (htmldocs)
produced this warning:

lib/bootconfig.c:911: warning: Function parameter or struct member 'early' not described in '_xbc_exit'
lib/bootconfig.c:911: warning: expecting prototype for xbc_exit(). Prototype was for _xbc_exit() instead

Introduced by commit

  aaeda6237dec ("bootconfig: use memblock_free_late to free xbc memory to buddy")

from the mm-hotfixes-unstable branch of the mm-hotfixes tree.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-04-16  7:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16  7:35 Stephen Rothwell [this message]
2024-04-16 18:51 ` linux-next: build warning after merge of the mm-hotfixes tree Andrew Morton
2024-04-17  5:29   ` Stephen Rothwell
2024-04-17 20:53     ` Andrew Morton
  -- 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=20240416173525.13bfd8dc@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=qiang4.zhang@intel.com \
    /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).