[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <43fd324c-585c-d85b-230c-5b086e1aaa2c@kernel.dk>
Date: Wed, 5 Apr 2023 13:26:46 -0600
From: Jens Axboe <axboe@...nel.dk>
To: wenyang.linux@...mail.com, Alexander Viro <viro@...iv.linux.org.uk>
Cc: Eric Biggers <ebiggers@...gle.com>, Christoph Hellwig <hch@....de>,
Dylan Yudaken <dylany@...com>,
David Woodhouse <dwmw@...zon.co.uk>, Fu Wei <wefu@...hat.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Michal Nazarewicz <m.nazarewicz@...sung.com>,
Matthew Wilcox <willy@...radead.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RESEND PATCH v2] eventfd: use
wait_event_interruptible_locked_irq() helper
On 4/5/23 1:20 PM, wenyang.linux@...mail.com wrote:
> From: Wen Yang <wenyang.linux@...mail.com>
>
> wait_event_interruptible_locked_irq was introduced by commit 22c43c81a51e
> ("wait_event_interruptible_locked() interface"), but older code such as
> eventfd_{write,read} still uses the open code implementation.
> Inspired by commit 8120a8aadb20
> ("fs/timerfd.c: make use of wait_event_interruptible_locked_irq()"), this
> patch replaces the open code implementation with a single macro call.
>
> No functional change intended.
Looks pretty reasonable to me. How did you test it?
--
Jens Axboe
Powered by blists - more mailing lists