From: Simon Horman <horms@kernel.org>
To: Shinas Rasheed <srasheed@marvell.com>
Cc: aayarekar@marvell.com, davem@davemloft.net, edumazet@google.com,
egallen@redhat.com, hgani@marvell.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, mschmidt@redhat.com,
netdev@vger.kernel.org, pabeni@redhat.com, sburla@marvell.com,
sedara@marvell.com, vburru@marvell.com, vimleshk@marvell.com
Subject: Re: [net PATCH v2] octeon_ep: fix tx dma unmap len values in SG
Date: Thu, 14 Sep 2023 12:57:59 +0200 [thread overview]
Message-ID: <20230914105759.GY401982@kernel.org> (raw)
In-Reply-To: <20230913084156.2147106-1-srasheed@marvell.com>
On Wed, Sep 13, 2023 at 01:41:56AM -0700, Shinas Rasheed wrote:
> Lengths of SG pointers are kept in the following order in
> the SG entries in hardware.
> 63 48|47 32|31 16|15 0
> -----------------------------------------
> | Len 0 | Len 1 | Len 2 | Len 3 |
> -----------------------------------------
> | Ptr 0 |
> -----------------------------------------
> | Ptr 1 |
> -----------------------------------------
> | Ptr 2 |
> -----------------------------------------
> | Ptr 3 |
> -----------------------------------------
> Dma pointers have to be unmapped based on their
> respective lengths given in this format.
>
> Fixes: 37d79d059606 ("octeon_ep: add Tx/Rx processing and interrupt support")
> Signed-off-by: Shinas Rasheed <srasheed@marvell.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2023-09-14 10:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 9:23 [net PATCH] octeon_ep: fix tx dma unmap len values in SG Shinas Rasheed
2023-09-11 18:01 ` Simon Horman
2023-09-12 7:04 ` Shinas Rasheed
2023-09-12 8:45 ` Paolo Abeni
2023-09-13 5:49 ` [EXT] " Shinas Rasheed
2023-09-13 8:41 ` [net PATCH v2] " Shinas Rasheed
2023-09-14 10:57 ` Simon Horman [this message]
2023-09-15 13:00 ` patchwork-bot+netdevbpf
[not found] ` <PH0PR18MB473404EA35ADAC222C9EB68FC7F1A@PH0PR18MB4734.namprd18.prod.outlook.com>
2023-09-12 19:45 ` [EXT] Re: [net PATCH] " Simon Horman
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=20230914105759.GY401982@kernel.org \
--to=horms@kernel.org \
--cc=aayarekar@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=egallen@redhat.com \
--cc=hgani@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sburla@marvell.com \
--cc=sedara@marvell.com \
--cc=srasheed@marvell.com \
--cc=vburru@marvell.com \
--cc=vimleshk@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.