All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Keller <jacob.e.keller@intel.com>
To: Jakub Kicinski <kuba@kernel.org>, <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <edumazet@google.com>,
	<pabeni@redhat.com>, <jiri@resnulli.us>
Subject: Re: [PATCH net 0/3] devlink: region snapshot locking fix and selftest adjustments
Date: Thu, 15 Dec 2022 10:42:22 -0800	[thread overview]
Message-ID: <f10175b1-edd6-4c58-7b00-59a5b2f71af5@intel.com> (raw)
In-Reply-To: <20221215020102.1619685-1-kuba@kernel.org>



On 12/14/2022 6:00 PM, Jakub Kicinski wrote:
> Minor fix for region snapshot locking and adjustments to selftests.
> 
> Jakub Kicinski (3):
>    devlink: hold region lock when flushing snapshots
>    selftests: devlink: fix the fd redirect in dummy_reporter_test
>    selftests: devlink: add a warning for interfaces coming up
> 
>   net/core/devlink.c                                  |  2 ++
>   .../selftests/drivers/net/netdevsim/devlink.sh      |  4 ++--
>   .../selftests/drivers/net/netdevsim/devlink_trap.sh | 13 +++++++++++++
>   3 files changed, 17 insertions(+), 2 deletions(-)
> 

Whole series makes sense.

Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>

  parent reply	other threads:[~2022-12-15 18:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15  2:00 [PATCH net 0/3] devlink: region snapshot locking fix and selftest adjustments Jakub Kicinski
2022-12-15  2:01 ` [PATCH net 1/3] devlink: hold region lock when flushing snapshots Jakub Kicinski
2022-12-15  8:38   ` Jiri Pirko
2022-12-15  2:01 ` [PATCH net 2/3] selftests: devlink: fix the fd redirect in dummy_reporter_test Jakub Kicinski
2022-12-15  2:01 ` [PATCH net 3/3] selftests: devlink: add a warning for interfaces coming up Jakub Kicinski
2022-12-15 18:42 ` Jacob Keller [this message]
2022-12-16 10:30 ` [PATCH net 0/3] devlink: region snapshot locking fix and selftest adjustments patchwork-bot+netdevbpf

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=f10175b1-edd6-4c58-7b00-59a5b2f71af5@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jiri@resnulli.us \
    --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 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.