netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Geoff Levand <geoff@infradead.org>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
	alexandr.lobakin@intel.com, alexander.duyck@gmail.com,
	pabeni@redhat.com
Subject: Re: [PATCH net v9 0/2] net/ps3_gelic_net: DMA related fixes
Date: Mon, 20 Mar 2023 10:30:18 +0000	[thread overview]
Message-ID: <167930821854.19842.2337685653320772957.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1679160765.git.geoff@infradead.org>

Hello:

This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Sat, 18 Mar 2023 17:39:15 +0000 you wrote:
> v9: Make rx_skb_size local to gelic_descr_prepare_rx.
> v8: Add more cpu_to_be32 calls.
> v7: Remove all cleanups, sync to spider net.
> v6: Reworked and cleaned up patches.
> v5: Some additional patch cleanups.
> v4: More patch cleanups.
> v3: Cleaned up patches as requested.
> 
> [...]

Here is the summary with links:
  - [net,v9,1/2] net/ps3_gelic_net: Fix RX sk_buff length
    https://git.kernel.org/netdev/net/c/19b3bb51c3bc
  - [net,v9,2/2] net/ps3_gelic_net: Use dma_mapping_error
    https://git.kernel.org/netdev/net/c/bebe933d35a6

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



      parent reply	other threads:[~2023-03-20 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-18 17:39 [PATCH net v9 0/2] net/ps3_gelic_net: DMA related fixes Geoff Levand
2023-03-18 17:39 ` [PATCH net v9 1/2] net/ps3_gelic_net: Fix RX sk_buff length Geoff Levand
2023-03-18 17:39 ` [PATCH net v9 2/2] net/ps3_gelic_net: Use dma_mapping_error Geoff Levand
2023-03-20 10:30 ` 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=167930821854.19842.2337685653320772957.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexander.duyck@gmail.com \
    --cc=alexandr.lobakin@intel.com \
    --cc=davem@davemloft.net \
    --cc=geoff@infradead.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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).