From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@savoirfairelinux.com,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH net-next] net: dsa: document missing functions
Date: Tue, 05 Apr 2016 22:02:25 -0400 [thread overview]
Message-ID: <87h9ffxzny.fsf@ketchup.mtl.sfl> (raw)
In-Reply-To: <20160405233943.GA19409@lunn.ch>
Hi Andrew,
Andrew Lunn <andrew@lunn.ch> writes:
> On Tue, Apr 05, 2016 at 11:22:40AM -0400, Vivien Didelot wrote:
>> Add description for the missing port_vlan_prepare, port_fdb_prepare,
>> port_fdb_dump functions in the DSA documentation.
>>
>> Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
>
> Hi Vivien
>
> A few English improvements:
>
>> ---
>> Documentation/networking/dsa/dsa.txt | 16 ++++++++++++++++
>> 1 file changed, 16 insertions(+)
>>
>> diff --git a/Documentation/networking/dsa/dsa.txt b/Documentation/networking/dsa/dsa.txt
>> index 3b196c3..8ba3369 100644
>> --- a/Documentation/networking/dsa/dsa.txt
>> +++ b/Documentation/networking/dsa/dsa.txt
>> @@ -542,6 +542,12 @@ Bridge layer
>> Bridge VLAN filtering
>> ---------------------
>>
>> +- port_vlan_prepare: bridge layer function invoked when the bridge prepares the
>> + configuration of a VLAN on the given port. If the operation is not
>> + programmable, this function should return -EOPNOTSUPP to inform the bridge
>
> s/programmable/supported by the hardware
>
>> + code to fallback to a software implementation. No hardware programmation
>
> s/programmation/setup
>
>> + must be done in this function. See port_vlan_add for this and details.
>> +
>> - port_vlan_add: bridge layer function invoked when a VLAN is configured
>> (tagged or untagged) for the given switch port
>>
>> @@ -552,6 +558,12 @@ Bridge VLAN filtering
>> function that the driver has to call for each VLAN the given port is a member
>> of. A switchdev object is used to carry the VID and bridge flags.
>>
>> +- port_fdb_prepare: bridge layer function invoked when the bridge prepares the
>> + installation of a Forwarding Database entry. If the operation is not
>> + programmable, this function should return -EOPNOTSUPP to inform the bridge
>
> s/programmable/supported
>
>> + code to fallback to a software implementation. No hardware programmation
>
> s/programmation/setup
Done, v2 on its way.
Thanks,
Vivien
prev parent reply other threads:[~2016-04-06 2:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 15:22 [PATCH net-next] net: dsa: document missing functions Vivien Didelot
2016-04-05 23:39 ` Andrew Lunn
2016-04-06 2:02 ` Vivien Didelot [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=87h9ffxzny.fsf@ketchup.mtl.sfl \
--to=vivien.didelot@savoirfairelinux.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kernel@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).