public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christoph Hellwig <hch@lst.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of Linus' tree
Date: Sun, 2 Feb 2025 19:56:35 -0700	[thread overview]
Message-ID: <8d47be36-c317-4392-a242-64d6c1727d46@kernel.dk> (raw)
In-Reply-To: <20250203125914.439f72fd@canb.auug.org.au>

On 2/2/25 6:59 PM, Stephen Rothwell wrote:
> Hi all,
> 
> After merging Linus' tree, today's linux-next build (sparc64
> defconfig) failed like this:
> 
> drivers/block/sunvdc.c: In function 'vdc_queue_drain':
> drivers/block/sunvdc.c:1130:9: error: too many arguments to function 'blk_mq_unquiesce_queue'
>  1130 |         blk_mq_unquiesce_queue(q, memflags);
>       |         ^~~~~~~~~~~~~~~~~~~~~~
> In file included from drivers/block/sunvdc.c:10:
> include/linux/blk-mq.h:895:6: note: declared here
>   895 | void blk_mq_unquiesce_queue(struct request_queue *q);
>       |      ^~~~~~~~~~~~~~~~~~~~~~
> drivers/block/sunvdc.c:1131:9: error: too few arguments to function 'blk_mq_unfreeze_queue'
>  1131 |         blk_mq_unfreeze_queue(q);
>       |         ^~~~~~~~~~~~~~~~~~~~~
> In file included from drivers/block/sunvdc.c:10:
> include/linux/blk-mq.h:914:1: note: declared here
>   914 | blk_mq_unfreeze_queue(struct request_queue *q, unsigned int memflags)
>       | ^~~~~~~~~~~~~~~~~~~~~
> 
> Caused by commit
> 
>   1e1a9cecfab3 ("block: force noio scope in blk_mq_freeze_queue")
> 
> I have applied the following fix:

Thanks Stephen, I've applied it to the block tree for 6.14.

-- 
Jens Axboe


  reply	other threads:[~2025-02-03  2:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03  1:59 linux-next: build failure after merge of Linus' tree Stephen Rothwell
2025-02-03  2:56 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-26  0:04 Stephen Rothwell
2024-09-26  7:36 ` Alice Ryhl
2024-09-26  8:13   ` Stephen Rothwell
2024-09-26  8:24     ` Miguel Ojeda
2024-09-26 12:49       ` Sedat Dilek
2024-09-26 12:58         ` Miguel Ojeda
2024-09-26 14:44           ` Sedat Dilek
2024-09-26 14:57             ` Miguel Ojeda
2020-04-20 11:35 Stephen Rothwell
2016-08-08  1:58 Stephen Rothwell
2016-08-08 15:37 ` Doug Ledford
2016-08-08 21:53   ` Stephen Rothwell
2016-08-08 23:30     ` Doug Ledford
2016-08-08 23:59       ` Stephen Rothwell
2016-08-09  8:54   ` Leon Romanovsky
2016-08-09 12:45     ` Doug Ledford
2015-10-07 22:44 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=8d47be36-c317-4392-a242-64d6c1727d46@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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