netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	linux-kernel@vger.kernel.org, bryan.whitehead@microchip.com,
	UNGLinuxDriver@microchip.com, Ian.Saturley@microchip.com
Subject: Re: [PATCH net-next V2 0/2] net: lan743x: Fix to use multiqueue start/stop APIs
Date: Fri, 09 Sep 2022 07:40:22 +0000	[thread overview]
Message-ID: <166270922288.30497.14233260513755591093.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220908082834.5070-1-Raju.Lakkaraju@microchip.com>

Hello:

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

On Thu, 8 Sep 2022 13:58:32 +0530 you wrote:
> This patch series address the fix to use multiqueue start/stop APIs and Add Rx IP and TCP checksum offload
> 
> Changes:
> ========
> V1 -> V2:
>  - Fix the sparse warnings
> 
> [...]

Here is the summary with links:
  - [net-next,V2,1/2] net: lan743x: Fix to use multiqueue start/stop APIs
    https://git.kernel.org/netdev/net-next/c/721f80c4d550
  - [net-next,V2,2/2] net: lan743x: Add support for Rx IP & TCP checksum offload
    https://git.kernel.org/netdev/net-next/c/cd6910501cfd

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



      parent reply	other threads:[~2022-09-09  7:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08  8:28 [PATCH net-next V2 0/2] net: lan743x: Fix to use multiqueue start/stop APIs Raju Lakkaraju
2022-09-08  8:28 ` [PATCH net-next V2 1/2] " Raju Lakkaraju
2022-09-08  8:28 ` [PATCH net-next V2 2/2] net: lan743x: Add support for Rx IP & TCP checksum offload Raju Lakkaraju
2022-09-09  7:40 ` 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=166270922288.30497.14233260513755591093.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Ian.Saturley@microchip.com \
    --cc=Raju.Lakkaraju@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=bryan.whitehead@microchip.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).