From: Yi Zhang <yi.zhang@redhat.com>
To: linux-block <linux-block@vger.kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>, asml.silence@gmail.com
Subject: [bug report] Compiling failed on latest linux-block/for-next
Date: Mon, 25 Oct 2021 23:26:10 +0800 [thread overview]
Message-ID: <CAHj4cs-Q7eLbrch63sQozd5p6jt2CaJLy2wywDNWA0=fUGHREQ@mail.gmail.com> (raw)
Hi Jens
Compiling the latest linux-block/for-next failed, pls check below log:
ca20d946ed42 (HEAD, origin/for-next, for-next) Merge branch
'for-5.16/block' into for-next
fa5fa8ec6077 block: refactor bio_iov_bvec_set()
54a88eb838d3 block: add single bio async direct IO helper
[root@fedora kernel]# make
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
CHK include/generated/compile.h
CHK kernel/kheaders_data.tar.xz
CC block/fops.o
block/fops.c: In function ‘blkdev_bio_end_io_async’:
block/fops.c:321:9: error: too many arguments to function ‘iocb->ki_complete’
321 | iocb->ki_complete(iocb, ret, 0);
| ^~~~
make[1]: *** [scripts/Makefile.build:277: block/fops.o] Error 1
make: *** [Makefile:1869: block] Error 2
--
Best Regards,
Yi Zhang
next reply other threads:[~2021-10-25 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 15:26 Yi Zhang [this message]
2021-10-25 15:35 ` [bug report] Compiling failed on latest linux-block/for-next Jens Axboe
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='CAHj4cs-Q7eLbrch63sQozd5p6jt2CaJLy2wywDNWA0=fUGHREQ@mail.gmail.com' \
--to=yi.zhang@redhat.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@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).