From: Sasha Levin <sashal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
io-uring <io-uring@vger.kernel.org>,
tglx@linutronix.de
Subject: Re: [GIT PULL] io_uring changes for 6.13-rc1
Date: Mon, 18 Nov 2024 17:24:19 -0500 [thread overview]
Message-ID: <Zzu-k1nW7LegRJEB@sashalap> (raw)
In-Reply-To: <Zzu6dkYTFX2AA26c@sashalap>
On Mon, Nov 18, 2024 at 05:06:46PM -0500, Sasha Levin wrote:
>Hi Jens, Thomas,
>
>On Mon, Nov 18, 2024 at 07:22:59AM -0700, Jens Axboe wrote:
>>hexue (1):
>> io_uring: add support for hybrid IOPOLL
>
>After merging of this pull request into linus-next, I've started seeing
>build errors:
>
>/builds/linux/io_uring/rw.c: In function 'io_hybrid_iopoll_delay':
>/builds/linux/io_uring/rw.c:1179:2: error: implicit declaration of function 'hrtimer_init_sleeper_on_stack'; did you mean 'hrtimer_setup_sleeper_on_stack'? [-Werror=implicit-function-declaration]
> hrtimer_init_sleeper_on_stack(&timer, CLOCK_MONOTONIC, mode);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> hrtimer_setup_sleeper_on_stack
>
>This is because 01ee194d1aba ("io_uring: add support for hybrid IOPOLL")
>adds a call to hrtimer_init_sleeper_on_stack() which was removed earlier
>today in Thomas's PR[1], specifically in commit f3bef7aaa6c8
>("hrtimers: Delete hrtimer_init_sleeper_on_stack()").
Linus,
Looks like this is a simple
s/hrtimer_init_sleeper_on_stack/hrtimer_setup_sleeper_on_stack , so this
issue could be addressed by replacing the new call with
hrtimer_setup_sleeper_on_stack() either in the io_uring or the
timers/core merge, whichever you pull last.
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-11-18 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 14:22 [GIT PULL] io_uring changes for 6.13-rc1 Jens Axboe
2024-11-18 22:06 ` Sasha Levin
2024-11-18 22:24 ` Sasha Levin [this message]
2024-11-18 23:27 ` Jens Axboe
2024-11-18 23:28 ` Jens Axboe
2024-11-19 1:10 ` pr-tracker-bot
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=Zzu-k1nW7LegRJEB@sashalap \
--to=sashal@kernel.org \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.