From: Shuo A Liu <shuo.a.liu@intel.com>
To: Yejune Deng <yejune.deng@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] virt: acrn: Use vfs_poll() instead of f_op->poll()
Date: Sat, 20 Feb 2021 17:48:42 +0800 [thread overview]
Message-ID: <20210220094842.GB30008@shuo-intel.sh.intel.com> (raw)
In-Reply-To: <20210219092612.7533-1-yejune.deng@gmail.com>
Thanks for the patch.
On Fri 19.Feb'21 at 17:26:12 +0800, Yejune Deng wrote:
>In acrn_irqfd_assign(), use vfs_poll() is a more advanced function,
>as the same time, modify the definition of events.
>
>Signed-off-by: Yejune Deng <yejune.deng@gmail.com>
>---
> drivers/virt/acrn/irqfd.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/drivers/virt/acrn/irqfd.c b/drivers/virt/acrn/irqfd.c
>index a8766d528e29..19890396e174 100644
>--- a/drivers/virt/acrn/irqfd.c
>+++ b/drivers/virt/acrn/irqfd.c
>@@ -112,9 +112,9 @@ static int acrn_irqfd_assign(struct acrn_vm *vm, struct acrn_irqfd *args)
> {
> struct eventfd_ctx *eventfd = NULL;
> struct hsm_irqfd *irqfd, *tmp;
>- unsigned int events;
> struct fd f;
> int ret = 0;
>+ __poll_t events;
Can you keep variable declarations is reverse fir tree order which this
driver follows?
>
> irqfd = kzalloc(sizeof(*irqfd), GFP_KERNEL);
> if (!irqfd)
>@@ -158,7 +158,7 @@ static int acrn_irqfd_assign(struct acrn_vm *vm, struct acrn_irqfd *args)
> mutex_unlock(&vm->irqfds_lock);
>
> /* Check the pending event in this stage */
>- events = f.file->f_op->poll(f.file, &irqfd->pt);
>+ events = vfs_poll(f.file, &irqfd->pt);
>
> if (events & POLLIN)
> acrn_irqfd_inject(irqfd);
>--
>2.29.0
>
next prev parent reply other threads:[~2021-02-20 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 9:26 Yejune Deng
2021-02-20 9:48 ` Shuo A Liu [this message]
2021-02-20 11:00 ` Yejune Deng
2021-02-20 14:53 Yejune Deng
2021-02-21 1:50 ` Liu, Shuo A
2021-02-21 7:54 ` Greg Kroah-Hartman
2021-02-21 13:11 ` Shuo A Liu
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=20210220094842.GB30008@shuo-intel.sh.intel.com \
--to=shuo.a.liu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yejune.deng@gmail.com \
/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
all inboxes | Powered by JetHome®