From: Sai Krishna <saikrishnag@marvell.com>
To: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <sgoutham@marvell.com>,
<gakula@marvell.com>, <lcherian@marvell.com>,
<jerinj@marvell.com>, <hkelam@marvell.com>, <sbhatta@marvell.com>,
<andrew+netdev@lunn.ch>, <bbhushan2@marvell.com>,
<nathan@kernel.org>, <ndesaulniers@google.com>,
<morbo@google.com>, <justinstitt@google.com>,
<llvm@lists.linux.dev>, <horms@kernel.org>
Cc: Sai Krishna <saikrishnag@marvell.com>
Subject: [net-next PATCH v3 0/2] octeontx2-af: fix build warnings flagged
Date: Tue, 11 Mar 2025 23:56:29 +0530 [thread overview]
Message-ID: <20250311182631.3224812-1-saikrishnag@marvell.com> (raw)
There are couple of build warnings observed on x86_64 flagged by Sparse.
Some are inconsistent usage of __iomem annotations and other Sparse
warnings are typecasting related. This patch series fixes the same.
Patch #1 This patch corrects the __iomem annotations flagged by Sparse.
Patch #2 This patch fixes rest of compiler warnings flagged by Sparse
which are related to typecasting to required datatype from
_iomem.
Sai Krishna (2):
octeontx2-af: correct __iomem annotations flagged by Sparse
octeontx2-af: fix compiler warnings flagged by Sparse
---
v3 changes:
Addressed review comments given by Simon Horman
1. Fixed compilation warnings reported by kernel test robot.
2. Addressed build warning fixes into separate patches.
v2 changes:
Addressed review comments given by Jakub Kicinski
Corrected Closes tag which was tampered by mail server.
drivers/net/ethernet/marvell/octeontx2/af/common.h | 2 +-
drivers/net/ethernet/marvell/octeontx2/af/rvu.c | 12 +++++++-----
.../net/ethernet/marvell/octeontx2/nic/otx2_common.c | 10 +++++-----
drivers/net/ethernet/marvell/octeontx2/nic/otx2_pf.c | 9 ++++-----
4 files changed, 17 insertions(+), 16 deletions(-)
--
2.25.1
next reply other threads:[~2025-03-11 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 18:26 Sai Krishna [this message]
2025-03-11 18:26 ` [net-next PATCH v3 1/2] octeontx2-af: correct __iomem annotations flagged by Sparse Sai Krishna
2025-03-11 21:22 ` Andrew Lunn
2025-04-14 16:38 ` Sai Krishna Gajula
2025-04-14 17:17 ` Andrew Lunn
2025-03-11 18:26 ` [net-next PATCH v3 2/2] octeontx2-af: fix compiler warnings " Sai Krishna
2025-03-11 21:32 ` Andrew Lunn
2025-05-26 9:15 ` Subbaraya Sundeep
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=20250311182631.3224812-1-saikrishnag@marvell.com \
--to=saikrishnag@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=horms@kernel.org \
--cc=jerinj@marvell.com \
--cc=justinstitt@google.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox