netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Vlad Yasevich <vyasevich@gmail.com>, shemminger@vyatta.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 1/2] bridge: display IFLA_BRPORT_LEARNING value
Date: Tue, 20 May 2014 18:11:59 +0200	[thread overview]
Message-ID: <537B7ECF.2020207@6wind.com> (raw)
In-Reply-To: <537B7130.2050504@gmail.com>

Le 20/05/2014 17:13, Vlad Yasevich a écrit :
> Hi Nicolas
>
> On 05/20/2014 05:37 AM, Nicolas Dichtel wrote:
>> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
>> ---
>>   bridge/link.c | 3 +++
>>   1 file changed, 3 insertions(+)
>>
>> diff --git a/bridge/link.c b/bridge/link.c
>> index 38dfaea2e180..1632bc16803f 100644
>> --- a/bridge/link.c
>> +++ b/bridge/link.c
>> @@ -185,6 +185,9 @@ int print_linkinfo(const struct sockaddr_nl *who,
>>   				if (prtb[IFLA_BRPORT_FAST_LEAVE])
>>   					print_onoff(fp, "fastleave",
>>   						    rta_getattr_u8(prtb[IFLA_BRPORT_FAST_LEAVE]));
>> +				if (prtb[IFLA_BRPORT_LEARNING])
>> +					print_onoff(fp, "learning",
>> +						    rta_getattr_u8(prtb[IFLA_BRPORT_LEARNING]));
>>   			}
>>   		} else
>>   			print_portstate(fp, rta_getattr_u8(tb[IFLA_PROTINFO]));
>>
>
> Already proposed. See http://patchwork.ozlabs.org/patch/350291/
Sorry for the noise, I've looked too quickly the patchwork.


Regards,
Nicolas

      reply	other threads:[~2014-05-20 16:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20  9:37 [PATCH iproute2 1/2] bridge: display IFLA_BRPORT_LEARNING value Nicolas Dichtel
2014-05-20  9:37 ` [PATCH iproute2 2/2] bridge: display IFLA_BRPORT_UNICAST_FLOOD value Nicolas Dichtel
2014-05-20 15:13 ` [PATCH iproute2 1/2] bridge: display IFLA_BRPORT_LEARNING value Vlad Yasevich
2014-05-20 16:11   ` Nicolas Dichtel [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=537B7ECF.2020207@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=vyasevich@gmail.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).