[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87egcgl1qe.fsf@ketchup.mtl.sfl>
Date: Sat, 13 Feb 2016 16:49:45 -0500
From: Vivien Didelot <vivien.didelot@...oirfairelinux.com>
To: Ido Schimmel <idosch@...lanox.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel@...oirfairelinux.com,
"David S. Miller" <davem@...emloft.net>,
Jiri Pirko <jiri@...nulli.us>,
Scott Feldman <sfeldma@...il.com>,
Nikolay Aleksandrov <nikolay@...ulusnetworks.com>,
Stephen Hemminger <stephen@...workplumber.org>,
Florian Fainelli <f.fainelli@...il.com>,
Andrew Lunn <andrew@...n.ch>
Subject: Re: [PATCH RFC 1/3] net: bridge: log state when setting it
Hi Ido,
Ido Schimmel <idosch@...lanox.com> writes:
> Fri, Feb 12, 2016 at 11:34:18PM IST, vivien.didelot@...oirfairelinux.com wrote:
>
> Hi Vivien,
>
>>Every call to br_set_state is followed by a call to br_log_state.
>>Directly call it within br_set_state instead.
>>
>>Signed-off-by: Vivien Didelot <vivien.didelot@...oirfairelinux.com>
>>---
>
> Maybe I'm missing something, but there are other instances of this
> pattern throughout the code, so why not convert them as well? See
> br_set_port_state() for example.
Good catch, I'll factorize that and send this as a unique patch then.
Thanks,
-v
Powered by blists - more mailing lists