All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Alex Elder <alex.elder@linaro.org>
Cc: Bert Karwatzki <spasswolf@web.de>, Alex Elder <elder@linaro.org>,
	Simon Horman <simon.horman@corigine.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	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: Tue, 30 May 2023 17:33:29 -0700	[thread overview]
Message-ID: <20230530173329.0fba5ec5@kernel.org> (raw)
In-Reply-To: <694f1e23-23bb-e184-6262-bfe3641a4f43@linaro.org>

On Tue, 30 May 2023 18:43:54 -0500 Alex Elder wrote:
> > 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.  
> 
> If the network maintainers can deal with your patch, I'm
> OK with it.  David et al if you want something else, please
> say so.

It's not correctly formatted. There are headers in the email body.

  reply	other threads:[~2023-05-31  0:33 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           ` [PATCH net v2] " Bert Karwatzki
2023-05-30 23:43             ` Alex Elder
2023-05-31  0:33               ` Jakub Kicinski [this message]
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=20230530173329.0fba5ec5@kernel.org \
    --to=kuba@kernel.org \
    --cc=alex.elder@linaro.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=elder@linaro.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 \
    --cc=spasswolf@web.de \
    /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.