linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@infradead.org>,
	"linux-fsdevel\@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-block\@vger.kernel.org" <linux-block@vger.kernel.org>,
	linux-aio@kvack.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v2] fs: replace the ki_complete two integer arguments with a single argument
Date: Thu, 21 Oct 2021 11:18:55 -0400	[thread overview]
Message-ID: <x49ee8ev21s.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <b7b6e63e-8787-f24c-2028-e147b91c4576@kernel.dk> (Jens Axboe's message of "Thu, 21 Oct 2021 08:44:16 -0600")

Jens Axboe <axboe@kernel.dk> writes:

> On 10/21/21 8:42 AM, Christoph Hellwig wrote:
>> On Thu, Oct 21, 2021 at 08:34:38AM -0600, Jens Axboe wrote:
>>> Incremental, are you happy with that comment?
>> 
>> Looks fine to me.
>
> OK good, can I add your ack/review? I can send out a v3 if needed, but
> seems a bit pointless for that small change.
>
> Jeff, are you happy with this one too?

> diff --git a/drivers/block/loop.c b/drivers/block/loop.c
> index 397bfafc4c25..66c6e0c5d638 100644
> --- a/drivers/block/loop.c
> +++ b/drivers/block/loop.c
> @@ -550,7 +550,7 @@ static void lo_rw_aio_do_completion(struct loop_cmd *cmd)
>  		blk_mq_complete_request(rq);
>  }
>  
> -static void lo_rw_aio_complete(struct kiocb *iocb, long ret, long ret2)
> +static void lo_rw_aio_complete(struct kiocb *iocb, u64 ret)
>  {
>  	struct loop_cmd *cmd = container_of(iocb, struct loop_cmd, iocb);
>  
> @@ -623,7 +623,7 @@ static int lo_rw_aio(struct loop_device *lo, struct loop_cmd *cmd,
>  	lo_rw_aio_do_completion(cmd);
>  
>  	if (ret != -EIOCBQUEUED)
> -		cmd->iocb.ki_complete(&cmd->iocb, ret, 0);
> +		lo_rw_aio_complete(&cmd->iocb, ret);
>  	return 0;

I'm not sure why that was part of this patch, but I think it's fine.

I've still got more testing to do, but you can add:

Reviewed-by: Jeff Moyer <jmoyer@redhat.com>

I'll follow up if there are issues.

Cheers,
Jeff


  parent reply	other threads:[~2021-10-21 15:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 19:08 [PATCH v2] fs: replace the ki_complete two integer arguments with a single argument Jens Axboe
2021-10-21  8:06 ` Greg KH
2021-10-21  8:32 ` Christoph Hellwig
2021-10-21 10:57   ` Christoph Hellwig
2021-10-21 14:34     ` Jens Axboe
2021-10-21 14:42       ` Christoph Hellwig
2021-10-21 14:44         ` Jens Axboe
2021-10-21 14:47           ` Christoph Hellwig
2021-10-21 15:18           ` Jeff Moyer [this message]
2021-10-21 15:19             ` Jens Axboe
2021-10-21 18:05               ` Jeff Moyer
2021-10-21 20:41                 ` Jens Axboe
2021-10-21 20:58                   ` Jeff Moyer
2021-10-21 21:03                     ` Jeff Moyer
2021-10-22 14:19                       ` Jens Axboe
2021-10-22 15:29                         ` Jens Axboe
2021-10-22 15:47                           ` 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=x49ee8ev21s.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=linux-aio@kvack.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-usb@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).