linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kent Overstreet <kent.overstreet@linux.dev>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	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 bcachefs tree
Date: Mon, 27 Nov 2023 09:46:34 +1100	[thread overview]
Message-ID: <20231127094634.12648f15@canb.auug.org.au> (raw)

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

Hi all,

After merging the bcachefs tree, today's linux-next build (x86_64
allmodconfig) produced this warning:

fs/bcachefs/buckets.c:337:21: warning: no previous prototype for 'bucket_m_to_alloc' [-Wmissing-prototypes]
  337 | struct bch_alloc_v4 bucket_m_to_alloc(struct bucket b)
      |                     ^~~~~~~~~~~~~~~~~

Introduced by commit

  8192d6956cb6 ("bcachefs: New bucket sector count helpers")

interacting with commit

  c6345dfa6e3e ("Makefile.extrawarn: turn on missing-prototypes globally")

from the mm tree.

It looks like this function should be static.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2023-11-26 22:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-26 22:46 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-01  5:16 linux-next: build warning after merge of the bcachefs tree Stephen Rothwell
2024-02-26  6:46 Stephen Rothwell
2024-01-17  2:28 Stephen Rothwell
2023-09-12  5:02 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=20231127094634.12648f15@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=kent.overstreet@linux.dev \
    --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).