All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, kuba@kernel.org, pkurapat@codeaurora.org,
	avuyyuru@codeaurora.org, bjorn.andersson@linaro.org,
	cpratapa@codeaurora.org, subashab@codeaurora.org,
	evgreen@chromium.org, elder@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: ipa: initialize all filter table slots
Date: Wed, 08 Sep 2021 11:20:05 +0000	[thread overview]
Message-ID: <163110000538.4441.10523758645271949269.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210907170554.399108-1-elder@linaro.org>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Tue,  7 Sep 2021 12:05:54 -0500 you wrote:
> There is an off-by-one problem in ipa_table_init_add(), when
> initializing filter tables.
> 
> In that function, the number of filter table entries is determined
> based on the number of set bits in the filter map.  However that
> count does *not* include the extra "slot" in the filter table that
> holds the filter map itself.  Meanwhile, ipa_table_addr() *does*
> include the filter map in the memory it returns, but because the
> count it's provided doesn't include it, it includes one too few
> table entries.
> 
> [...]

Here is the summary with links:
  - [net] net: ipa: initialize all filter table slots
    https://git.kernel.org/netdev/net/c/b5c102238cea

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2021-09-08 11:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07 17:05 [PATCH net] net: ipa: initialize all filter table slots Alex Elder
2021-09-08 11:20 ` patchwork-bot+netdevbpf [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=163110000538.4441.10523758645271949269.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=avuyyuru@codeaurora.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=cpratapa@codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=elder@kernel.org \
    --cc=elder@linaro.org \
    --cc=evgreen@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pkurapat@codeaurora.org \
    --cc=subashab@codeaurora.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 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.