netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bert Karwatzki <spasswolf@web.de>
To: Alex Elder <elder@linaro.org>, Simon Horman <simon.horman@corigine.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	 Jakub Kicinski <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org,  linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: ipa: Use the correct value for IPA_STATUS_SIZE
Date: Wed, 31 May 2023 01:25:20 +0200	[thread overview]
Message-ID: <dcfb1ccd722af0e9c215c518ec2cd7a8602d2127.camel@web.de> (raw)
In-Reply-To: <f9ccdc27-7b5f-5894-46ab-84c1e1650d9f@linaro.org>

From 2e5e4c07606a100fd4af0f08e4cd158f88071a3a Mon Sep 17 00:00:00 2001
From: Bert Karwatzki <spasswolf@web.de>
To: davem@davemloft.net
To: edumazet@google.com
To: kuba@kernel.org
To: pabeni@redhat.com
Cc: elder@kernel.org
Cc: netdev@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Date: Wed, 31 May 2023 00:16:33 +0200
Subject: [PATCH net v2] net: ipa: Use correct value for IPA_STATUS_SIZE

IPA_STATUS_SIZE was introduced in commit b8dc7d0eea5a as a replacement
for the size of the removed struct ipa_status which had size
sizeof(__le32[8]). Use this value as IPA_STATUS_SIZE.

Fixes: b8dc7d0eea5a ("net: ipa: stop using sizeof(status)")
Signed-off-by: Bert Karwatzki <spasswolf@web.de>
---
 drivers/net/ipa/ipa_endpoint.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/ipa/ipa_endpoint.c b/drivers/net/ipa/ipa_endpoint.c
index 2ee80ed140b7..afa1d56d9095 100644
--- a/drivers/net/ipa/ipa_endpoint.c
+++ b/drivers/net/ipa/ipa_endpoint.c
@@ -119,7 +119,7 @@ enum ipa_status_field_id {
 };
 
 /* Size in bytes of an IPA packet status structure */
-#define IPA_STATUS_SIZE			sizeof(__le32[4])
+#define IPA_STATUS_SIZE			sizeof(__le32[8])
 
 /* IPA status structure decoder; looks up field values for a structure */
 static u32 ipa_status_extract(struct ipa *ipa, const void *data,
-- 
2.40.1

As I'm sure that git send-email didn't work (probably due to sendmail/exim
configuration issues), I'm sending this from evolution again.

Bert Karwatzki
 

  reply	other threads:[~2023-05-30 23:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-27 20:46 [PATCH net] net: ipa: Use the correct value for IPA_STATUS_SIZE Bert Karwatzki
2023-05-30  5:10 ` Jakub Kicinski
2023-05-30  7:09 ` Simon Horman
2023-05-30  9:10   ` Bert Karwatzki
2023-05-30 12:29     ` Alex Elder
2023-05-30 18:36       ` Bert Karwatzki
2023-05-30 19:04         ` Alex Elder
2023-05-30 23:25           ` Bert Karwatzki [this message]
2023-05-30 23:43             ` [PATCH net v2] " Alex Elder
2023-05-31  0:33               ` Jakub Kicinski
2023-05-31  1:57               ` Alex Elder
2023-05-31 10:36                 ` [PATCH net v3] net: ipa: Use " Bert Karwatzki
2023-05-31 22:07                   ` Simon Horman
2023-06-01 11:40                   ` patchwork-bot+netdevbpf

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=dcfb1ccd722af0e9c215c518ec2cd7a8602d2127.camel@web.de \
    --to=spasswolf@web.de \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=elder@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=simon.horman@corigine.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;
as well as URLs for NNTP newsgroup(s).