From: John Hubbard <jhubbard@nvidia.com>
To: Jakob Koschel <jakobkoschel@gmail.com>,
Matt Porter <mporter@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org,
Alexandre Bounine <alex.bou9@gmail.com>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>,
Brian Johannesmeyer <bjohannesmeyer@gmail.com>,
Cristiano Giuffrida <c.giuffrida@vu.nl>,
"Bos, H.J." <h.j.bos@vu.nl>
Subject: Re: [PATCH] rapidio: remove unnecessary use of list iterator
Date: Sun, 20 Mar 2022 15:50:55 -0700 [thread overview]
Message-ID: <82bcda66-cf26-c9f5-fe2e-e41f739ec1ff@nvidia.com> (raw)
In-Reply-To: <20220319203344.2547702-1-jakobkoschel@gmail.com>
On 3/19/22 13:33, Jakob Koschel wrote:
> req->map is set in the valid case and always equals 'map' if the break
> was hit. It therefore is unnecessary to use the list iterator variable
> and the use of 'map' can be replaced with req->map.
>
> This is done in preparation to limit the scope of a list iterator to
> the list traversal loop [1].
>
> Link: https://lore.kernel.org/all/YhdfEIwI4EdtHdym@kroah.com/
> Signed-off-by: Jakob Koschel <jakobkoschel@gmail.com>
> ---
> drivers/rapidio/devices/rio_mport_cdev.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/rapidio/devices/rio_mport_cdev.c b/drivers/rapidio/devices/rio_mport_cdev.c
> index 7df466e22282..2cdc054e53a5 100644
> --- a/drivers/rapidio/devices/rio_mport_cdev.c
> +++ b/drivers/rapidio/devices/rio_mport_cdev.c
> @@ -915,7 +915,7 @@ rio_dma_transfer(struct file *filp, u32 transfer_mode,
> goto err_req;
> }
>
> - if (xfer->length + xfer->offset > map->size) {
> + if (xfer->length + xfer->offset > req->map->size) {
> ret = -EINVAL;
> goto err_req;
> }
> @@ -927,7 +927,7 @@ rio_dma_transfer(struct file *filp, u32 transfer_mode,
> }
>
> sg_set_buf(req->sgt.sgl,
> - map->virt_addr + (baddr - map->phys_addr) +
> + req->map->virt_addr + (baddr - req->map->phys_addr) +
> xfer->offset, xfer->length);
> }
I'm not a RapidIO expert, but this change is small and clearly correct,
so:
Reviewed-by: John Hubbard <jhubbard@nvidia.com>
thanks,
--
John Hubbard
NVIDIA
>
>
> base-commit: 34e047aa16c0123bbae8e2f6df33e5ecc1f56601
> --
> 2.25.1
>
prev parent reply other threads:[~2022-03-20 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 20:33 [PATCH] rapidio: remove unnecessary use of list iterator Jakob Koschel
2022-03-20 22:50 ` John Hubbard [this message]
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=82bcda66-cf26-c9f5-fe2e-e41f739ec1ff@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=alex.bou9@gmail.com \
--cc=bjohannesmeyer@gmail.com \
--cc=c.giuffrida@vu.nl \
--cc=h.j.bos@vu.nl \
--cc=jakobkoschel@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mporter@kernel.crashing.org \
--cc=rppt@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