From: David Miller <davem@davemloft.net>
To: kuba@kernel.org
Cc: netdev@vger.kernel.org, kernel-team@fb.com, eugenem@fb.com,
jacob.e.keller@intel.com, jiri@resnulli.us,
michael.chan@broadcom.com, snelson@pensando.io,
jesse.brandeburg@intel.com, rdunlap@infradead.org,
vasundhara-v.volam@broadcom.com
Subject: Re: [PATCH net-next v3] devlink: expand the devlink-info documentation
Date: Tue, 24 Mar 2020 16:49:06 -0700 (PDT) [thread overview]
Message-ID: <20200324.164906.998922318294541493.davem@davemloft.net> (raw)
In-Reply-To: <20200324173016.135105-1-kuba@kernel.org>
From: Jakub Kicinski <kuba@kernel.org>
Date: Tue, 24 Mar 2020 10:30:16 -0700
> We are having multiple review cycles with all vendors trying
> to implement devlink-info. Let's expand the documentation with
> more information about what's implemented and motivation behind
> this interface in an attempt to make the implementations easier.
>
> Describe what each info section is supposed to contain, and make
> some references to other HW interfaces (PCI caps).
>
> Document how firmware management is expected to look, to make
> it clear how devlink-info and devlink-flash work in concert.
>
> Name some future work.
>
> v2: - improve wording
> v3: - improve wording
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Applied, thanks.
prev parent reply other threads:[~2020-03-24 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 17:30 [PATCH net-next v3] devlink: expand the devlink-info documentation Jakub Kicinski
2020-03-24 23:49 ` David Miller [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=20200324.164906.998922318294541493.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eugenem@fb.com \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=kernel-team@fb.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=snelson@pensando.io \
--cc=vasundhara-v.volam@broadcom.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).