public inbox for linux-kernel@vger.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, elder@kernel.org,
	evgreen@chromium.org, bjorn.andersson@linaro.org,
	cpratapa@codeaurora.org, subashab@codeaurora.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/6] net: ipa: hardware pipeline cleanup fixes
Date: Fri, 29 Jan 2021 04:50:13 +0000	[thread overview]
Message-ID: <161189581338.32508.15067215532800740787.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210126185703.29087-1-elder@linaro.org>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Tue, 26 Jan 2021 12:56:57 -0600 you wrote:
> Version 2 of this series fixes a "restricted __le16 degrades to
> integer" warning from sparse in the third patch.  The normal host
> architecture is little-endian, so the problem did not produce
> incorrect behavior, but the code was wrong not to perform the
> endianness conversion.  The updated patch uses le16_get_bits() to
> properly extract the value of the field we're interested in.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/6] net: ipa: rename "tag status" symbols
    https://git.kernel.org/netdev/net-next/c/aa56e3e5cdb4
  - [net-next,v2,2/6] net: ipa: minor update to handling of packet with status
    https://git.kernel.org/netdev/net-next/c/162fbc6f4519
  - [net-next,v2,3/6] net: ipa: drop packet if status has valid tag
    https://git.kernel.org/netdev/net-next/c/f6aba7b5199a
  - [net-next,v2,4/6] net: ipa: signal when tag transfer completes
    https://git.kernel.org/netdev/net-next/c/51c48ce264f8
  - [net-next,v2,5/6] net: ipa: don't pass tag value to ipa_cmd_ip_tag_status_add()
    https://git.kernel.org/netdev/net-next/c/792b75b14786
  - [net-next,v2,6/6] net: ipa: don't pass size to ipa_cmd_transfer_add()
    https://git.kernel.org/netdev/net-next/c/070740d389aa

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



      parent reply	other threads:[~2021-01-29  4:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26 18:56 [PATCH net-next v2 0/6] net: ipa: hardware pipeline cleanup fixes Alex Elder
2021-01-26 18:56 ` [PATCH net-next v2 1/6] net: ipa: rename "tag status" symbols Alex Elder
2021-01-26 18:56 ` [PATCH net-next v2 2/6] net: ipa: minor update to handling of packet with status Alex Elder
2021-01-26 18:57 ` [PATCH net-next v2 3/6] net: ipa: drop packet if status has valid tag Alex Elder
2021-01-26 18:57 ` [PATCH net-next v2 4/6] net: ipa: signal when tag transfer completes Alex Elder
2021-01-26 18:57 ` [PATCH net-next v2 5/6] net: ipa: don't pass tag value to ipa_cmd_ip_tag_status_add() Alex Elder
2021-01-26 18:57 ` [PATCH net-next v2 6/6] net: ipa: don't pass size to ipa_cmd_transfer_add() Alex Elder
2021-01-27 14:39 ` [PATCH net-next v2 0/6] net: ipa: hardware pipeline cleanup fixes Willem de Bruijn
2021-01-29  4:50 ` 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=161189581338.32508.15067215532800740787.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox