Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Thomas Falcon <tlfalcon@linux.ibm.com>
Cc: netdev@vger.kernel.org, drt@linux.vnet.ibm.com,
sukadev@linux.vnet.ibm.com, ljp@linux.vnet.ibm.com,
cforno12@linux.ibm.com
Subject: Re: [PATCH net-next 5/5] ibmvnic: Provide documentation for ACL sysfs files
Date: Mon, 31 Aug 2020 12:26:53 -0700 [thread overview]
Message-ID: <20200831122653.5bdef2f4@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <1598893093-14280-6-git-send-email-tlfalcon@linux.ibm.com>
On Mon, 31 Aug 2020 11:58:13 -0500 Thomas Falcon wrote:
> Provide documentation for ibmvnic device Access Control List
> files.
What API is used to set those parameters in the first place?
next prev parent reply other threads:[~2020-08-31 19:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 16:58 [PATCH net-next 0/5] ibmvnic: Report ACL settings in sysfs Thomas Falcon
2020-08-31 16:58 ` [PATCH net-next 1/5] ibmvnic: Create failover sysfs as part of an attribute group Thomas Falcon
2020-08-31 16:58 ` [PATCH net-next 2/5] ibmvnic: Include documentation for ibmvnic sysfs files Thomas Falcon
2020-08-31 19:07 ` Jakub Kicinski
2020-08-31 19:51 ` Thomas Falcon
2020-08-31 16:58 ` [PATCH net-next 3/5] ibmvnic: Remove ACL change indication definitions Thomas Falcon
2020-08-31 16:58 ` [PATCH net-next 4/5] ibmvnic: Reporting device ACL settings through sysfs Thomas Falcon
2020-09-02 21:51 ` Sukadev Bhattiprolu
2020-08-31 16:58 ` [PATCH net-next 5/5] ibmvnic: Provide documentation for ACL sysfs files Thomas Falcon
2020-08-31 19:26 ` Jakub Kicinski [this message]
2020-08-31 19:54 ` Thomas Falcon
2020-08-31 20:11 ` Jakub Kicinski
2020-08-31 21:44 ` Thomas Falcon
2020-08-31 22:00 ` Jakub Kicinski
2020-08-31 22:17 ` David Miller
2020-08-31 22:30 ` Thomas Falcon
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=20200831122653.5bdef2f4@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=cforno12@linux.ibm.com \
--cc=drt@linux.vnet.ibm.com \
--cc=ljp@linux.vnet.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=sukadev@linux.vnet.ibm.com \
--cc=tlfalcon@linux.ibm.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).