netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: davem@davemloft.net, jiri@resnulli.us, netdev@vger.kernel.org,
	oss-drivers@netronome.com, mkubecek@suse.cz, andrew@lunn.ch
Subject: Re: [RFC iproute2] devlink: add support for updating device flash
Date: Tue, 19 Feb 2019 15:28:08 -0800	[thread overview]
Message-ID: <20190219152808.09348237@shemminger-XPS-13-9360> (raw)
In-Reply-To: <20190211065923.22670-5-jakub.kicinski@netronome.com>

On Sun, 10 Feb 2019 22:59:23 -0800
Jakub Kicinski <jakub.kicinski@netronome.com> wrote:

> Add new command for updating flash of devices via devlink API.
> Example:
> 
> $ cp flash-boot.bin /lib/firmware/
> $ devlink dev flash pci/0000:05:00.0 file flash-boot.bin
> 
> Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>

This is targeted at iproute2-next since it needs stuff from net-next.


      reply	other threads:[~2019-02-19 23:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11  6:59 [RFC 0/3] devlink: add the ability to update device flash Jakub Kicinski
2019-02-11  6:59 ` [RFC 1/3] devlink: add flash update command Jakub Kicinski
2019-02-11 16:45   ` Jiri Pirko
2019-02-11 19:25     ` [oss-drivers] " Jakub Kicinski
2019-02-12  7:26       ` Jiri Pirko
2019-02-11  6:59 ` [RFC 2/3] ethtool: add compat for flash update Jakub Kicinski
2019-02-11  6:59 ` [RFC 3/3] nfp: devlink: allow flashing the device via devlink Jakub Kicinski
2019-02-11  6:59 ` [RFC iproute2] devlink: add support for updating device flash Jakub Kicinski
2019-02-19 23:28   ` Stephen Hemminger [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=20190219152808.09348237@shemminger-XPS-13-9360 \
    --to=stephen@networkplumber.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=jakub.kicinski@netronome.com \
    --cc=jiri@resnulli.us \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.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 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).