netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: netdev@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Jiri Pirko <jiri@nvidia.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	David Ahern <dsahern@kernel.org>,
	Stephen Hemminger <stephen@networkplumber.org>,
	linux-doc@vger.kernel.org, intel-wired-lan@lists.osuosl.org
Subject: Re: [net-next v2 0/2] devlink: implement dry run support for flash update
Date: Thu, 21 Jul 2022 16:52:56 -0700	[thread overview]
Message-ID: <20220721165256.02f83fe8@kernel.org> (raw)
In-Reply-To: <20220721211451.2475600-1-jacob.e.keller@intel.com>

On Thu, 21 Jul 2022 14:14:45 -0700 Jacob Keller wrote:
> This is a re-send of the dry run support I submitted nearly a year ago at
> https://lore.kernel.org/netdev/CO1PR11MB50898047B9C0FAA520505AFDD6B59@CO1PR11MB5089.namprd11.prod.outlook.com/

You confused patchwork, please post user space in separate thread:

https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html#how-do-i-post-corresponding-changes-to-user-space-components

Tomorrow:

https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html#i-have-received-review-feedback-when-should-i-post-a-revised-version-of-the-patches

      parent reply	other threads:[~2022-07-21 23:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 21:14 [net-next v2 0/2] devlink: implement dry run support for flash update Jacob Keller
2022-07-21 21:14 ` [net-next v2 1/2] devlink: add dry run attribute to " Jacob Keller
2022-07-22  6:26   ` Jiri Pirko
2022-07-22 21:13     ` Keller, Jacob E
2022-07-21 21:14 ` [net-next v2 2/2] ice: support dry run of a flash update to validate firmware file Jacob Keller
2022-07-21 21:14 ` [iproute2-next v2 0/3] devlink: support dry run attribute for flash update Jacob Keller
2022-07-21 21:14 ` [iproute2-next v2 1/3] update <linux/devlink.h> UAPI header Jacob Keller
2022-07-21 21:14 ` [iproute2-next v2 2/3] mnlg: add function to get CTRL_ATTR_MAXATTR value Jacob Keller
2022-07-21 21:14 ` [iproute2-next v2 3/3] devlink: add dry run attribute support to devlink flash Jacob Keller
2022-07-22  6:22   ` Jiri Pirko
2022-07-22 21:14     ` Keller, Jacob E
2022-07-21 23:52 ` Jakub Kicinski [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=20220721165256.02f83fe8@kernel.org \
    --to=kuba@kernel.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jacob.e.keller@intel.com \
    --cc=jiri@nvidia.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stephen@networkplumber.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).