All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jonathan Toppins <jtoppins@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: [net-next v2 0/2] bonding: netlink errors and cleanup
Date: Fri, 10 Jun 2022 06:20:13 +0000	[thread overview]
Message-ID: <165484201346.1106.1962248931865543911.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1654711315.git.jtoppins@redhat.com>

Hello:

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

On Wed,  8 Jun 2022 14:14:55 -0400 you wrote:
> The first patch attempts to set helpful error messages when
> configuring bonds via netlink. The second patch removes redundant
> init code for RLB mode which is already done in bond_open.
> 
> v2:
>  * rebased to latest net-next
>  * fixed kernel doc header for __bond_opt_set
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/2] bonding: netlink error message support for options
    https://git.kernel.org/netdev/net-next/c/2bff369b2354
  - [net-next,v2,2/2] bonding: cleanup bond_create
    https://git.kernel.org/netdev/net-next/c/2fa3ee93d13c

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-06-10  6:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 18:14 [net-next v2 0/2] bonding: netlink errors and cleanup Jonathan Toppins
2022-06-08 18:14 ` [net-next v2 1/2] bonding: netlink error message support for options Jonathan Toppins
2022-06-08 18:52   ` Jay Vosburgh
2022-06-08 18:14 ` [net-next v2 2/2] bonding: cleanup bond_create Jonathan Toppins
2022-06-08 18:51   ` Jay Vosburgh
2022-06-10  6: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=165484201346.1106.1962248931865543911.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=jtoppins@redhat.com \
    --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 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.