public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
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>,
	Jason Cobham <jcobham@questertangent.com>
Subject: Re: [PATCH net-next v2 0/3] net: dsa: check out-of-range ageing time
Date: Wed, 15 Mar 2017 22:05:56 +0100	[thread overview]
Message-ID: <20170315210556.GA7416@lunn.ch> (raw)
In-Reply-To: <20170315195350.11059-1-vivien.didelot@savoirfairelinux.com>

> This patchset fixes this by adding ageing_time_min and ageing_time_max
> fields to the dsa_switch structure, which can optionally be set by a DSA
> driver.
> 
> If provided, the DSA core will check for out-of-range values in the
> SWITCHDEV_ATTR_ID_BRIDGE_AGEING_TIME prepare phase and return -ERANGE
> accordingly.
> 
> Finally set these limits in the mv88e6xxx driver.

Hi Vivien

Thanks for doing it this way. Nicely done.

Reviewed-by: Andrew Lunn <andrew@lunn.ch>

    Andrew

  parent reply	other threads:[~2017-03-15 21:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15 19:53 [PATCH net-next v2 0/3] net: dsa: check out-of-range ageing time Vivien Didelot
2017-03-15 19:53 ` [PATCH net-next v2 1/3] net: dsa: dsa_fastest_ageing_time return unsigned Vivien Didelot
2017-03-15 20:03   ` Florian Fainelli
2017-03-15 19:53 ` [PATCH net-next v2 2/3] net: dsa: check out-of-range ageing time value Vivien Didelot
2017-03-15 20:04   ` Florian Fainelli
2017-03-15 19:53 ` [PATCH net-next v2 3/3] net: dsa: mv88e6xxx: specify ageing time limits Vivien Didelot
2017-03-15 20:04   ` Florian Fainelli
2017-03-15 21:05 ` Andrew Lunn [this message]
2017-03-15 22:34 ` [PATCH net-next v2 0/3] net: dsa: check out-of-range ageing time David Miller

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=20170315210556.GA7416@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=jcobham@questertangent.com \
    --cc=kernel@savoirfairelinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@savoirfairelinux.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