All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Parav Pandit <parav@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
	vadim.fedorenko@linux.dev, jiri@resnulli.us
Subject: Re: [PATCH net-next v2 0/2] devlink port attr cleanup
Date: Fri, 15 Aug 2025 00:50:25 +0000	[thread overview]
Message-ID: <175521902523.500228.15621849606665277233.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250813094417.7269-1-parav@nvidia.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 13 Aug 2025 12:44:15 +0300 you wrote:
> Hi,
> 
> This two small patches simplifies the devlink port attributes set
> functions.
> 
> Summary:
> patch-1 removes the return 0 check at several places and simplfies
> patch-2 constifies the attributes and moves the checks early
> caller
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/2] devlink/port: Simplify return checks
    https://git.kernel.org/netdev/net-next/c/0ebc0bcd0aa0
  - [net-next,v2,2/2] devlink/port: Check attributes early and constify
    https://git.kernel.org/netdev/net-next/c/41a6e8ab1864

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



      parent reply	other threads:[~2025-08-15  0:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-13  9:44 [PATCH net-next v2 0/2] devlink port attr cleanup Parav Pandit
2025-08-13  9:44 ` [PATCH net-next v2 1/2] devlink/port: Simplify return checks Parav Pandit
2025-08-13  9:44 ` [PATCH net-next v2 2/2] devlink/port: Check attributes early and constify Parav Pandit
2025-08-15  0: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=175521902523.500228.15621849606665277233.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=parav@nvidia.com \
    --cc=vadim.fedorenko@linux.dev \
    /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.