From: David Ahern <dsahern@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org,
jakub.kicinski@netronome.com, saeedm@mellanox.com,
mlxsw@mellanox.com, f.fainelli@gmail.com
Subject: Re: [patch iproute2-next v4 0/2] devlink: couple forgotten flash patches
Date: Mon, 16 Sep 2019 08:49:11 -0600 [thread overview]
Message-ID: <7d3ad854-deba-45e2-fb10-b5a9c9587a04@gmail.com> (raw)
In-Reply-To: <20190916100924.GM2286@nanopsycho.orion>
On 9/16/19 4:09 AM, Jiri Pirko wrote:
> The fact that the file is expected to be in /lib/firmware is in the
> devlink flash description right above:
>
>
> devlink dev flash - write device's non-volatile memory.
> DEV - specifies the devlink device to write to.
>
> file PATH - Path to the file which will be written into device's flash. The path needs to be relative to one of the directories
> searched by the kernel firmware loaded, such as /lib/firmware.
fine. applied both to iproute2-next.
prev parent reply other threads:[~2019-09-16 14:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 11:29 [patch iproute2-next v4 0/2] devlink: couple forgotten flash patches Jiri Pirko
2019-09-12 11:29 ` [patch iproute2-next v4 1/2] devlink: implement flash update status monitoring Jiri Pirko
2019-09-12 11:29 ` [patch iproute2-next v4 2/2] devlink: implement flash " Jiri Pirko
2019-09-13 17:25 ` [patch iproute2-next v4 0/2] devlink: couple forgotten flash patches David Ahern
2019-09-14 6:00 ` Jiri Pirko
2019-09-15 17:58 ` David Ahern
2019-09-16 5:31 ` Jiri Pirko
2019-09-16 10:09 ` Jiri Pirko
2019-09-16 14:49 ` David Ahern [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=7d3ad854-deba-45e2-fb10-b5a9c9587a04@gmail.com \
--to=dsahern@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@resnulli.us \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.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