From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>,
Christophe Leroy <christophe.leroy@c-s.fr>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: LKML <linux-kernel@vger.kernel.org>, stable@vger.kernel.org
Subject: Re: Build failure on latest powerpc/merge (311ae9e159d8 io_uring: fix dead-hung for non-iter fixed rw)
Date: Fri, 29 Nov 2019 21:07:49 +0300 [thread overview]
Message-ID: <38cb2865-d887-d46d-94ef-4ebccff4dc60@gmail.com> (raw)
In-Reply-To: <5389b43a-259d-997c-41e6-5e84a91b012a@kernel.dk>
[-- Attachment #1.1: Type: text/plain, Size: 531 bytes --]
On 29/11/2019 20:16, Jens Axboe wrote:
> On 11/29/19 8:14 AM, Christophe Leroy wrote:
>>>>
>>>> Reverting commit 311ae9e159d8 ("io_uring: fix dead-hung for non-iter
>>>> fixed rw") clears the failure.
>>>>
>>>> Most likely an #include is missing.
>>>
>>> Huh weird how the build bots didn't catch that. Does the below work?
>>
>> Yes it works, thanks.
>
> Thanks for reporting and testing, I've queued it up with your reported
> and tested-by.
>
My bad, thanks for the report and fixing.
--
Pavel Begunkov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-01 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 14:53 Build failure on latest powerpc/merge (311ae9e159d8 io_uring: fix dead-hung for non-iter fixed rw) Christophe Leroy
2019-11-29 16:04 ` Jens Axboe
2019-11-29 16:14 ` Christophe Leroy
2019-11-29 17:16 ` Jens Axboe
2019-11-29 18:07 ` Pavel Begunkov [this message]
2019-11-29 20:45 ` Jens Axboe
2019-12-03 9:06 ` Geert Uytterhoeven
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=38cb2865-d887-d46d-94ef-4ebccff4dc60@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stable@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).