From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, kernel-team@fb.com,
jacob.e.keller@intel.com
Subject: Re: [PATCH net-next v3 3/3] docs: devlink: clarify the scope of snapshot id
Date: Fri, 1 May 2020 10:59:28 +0200 [thread overview]
Message-ID: <20200501085928.GI6581@nanopsycho.orion> (raw)
In-Reply-To: <20200430175759.1301789-4-kuba@kernel.org>
Thu, Apr 30, 2020 at 07:57:58PM CEST, kuba@kernel.org wrote:
>In past discussions Jiri explained snapshot ids are cross-region.
>Explain this in the docs.
>
>v3: new patch
>
>Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Reviewed-by: Jiri Pirko <jiri@mellanox.com>
next prev parent reply other threads:[~2020-05-01 8:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 17:57 [PATCH net-next v3 0/3] devlink: kernel region snapshot id allocation Jakub Kicinski
2020-04-30 17:57 ` [PATCH net-next v3 1/3] devlink: factor out building a snapshot notification Jakub Kicinski
2020-05-01 8:51 ` Jiri Pirko
2020-05-01 21:27 ` Jacob Keller
2020-04-30 17:57 ` [PATCH net-next v3 2/3] devlink: let kernel allocate region snapshot id Jakub Kicinski
2020-05-01 8:59 ` Jiri Pirko
2020-05-01 21:32 ` Jacob Keller
2020-04-30 17:57 ` [PATCH net-next v3 3/3] docs: devlink: clarify the scope of " Jakub Kicinski
2020-05-01 8:59 ` Jiri Pirko [this message]
2020-05-01 21:34 ` Jacob Keller
2020-04-30 17:57 ` [PATCH iproute2-next v3] devlink: support kernel-side snapshot id allocation Jakub Kicinski
2020-05-02 5:58 ` Jiri Pirko
2020-05-05 16:14 ` David Ahern
2020-05-05 16:20 ` Jakub Kicinski
2020-05-05 16:59 ` David Ahern
2020-05-05 17:04 ` [PATCH iproute2-next RESEND] " Jakub Kicinski
2020-05-05 17:11 ` David Ahern
2020-05-05 17:05 ` [PATCH iproute2-next v3] " Jakub Kicinski
2020-05-05 17:06 ` Jakub Kicinski
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=20200501085928.GI6581@nanopsycho.orion \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=jacob.e.keller@intel.com \
--cc=kernel-team@fb.com \
--cc=kuba@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).