netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: David Miller <davem@davemloft.net>
Cc: nikolay@cumulusnetworks.com, amarao@servers.com,
	netdev@vger.kernel.org, jiri@resnulli.us
Subject: Re: [RFT iproute2] iplink_bridge: scale all time values by USER_HZ
Date: Sat, 25 Jul 2020 20:17:58 -0700	[thread overview]
Message-ID: <20200725201758.4cfae512@hermes.lan> (raw)
In-Reply-To: <20200724.173112.451428196025351292.davem@davemloft.net>

On Fri, 24 Jul 2020 17:31:12 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:

> From: nikolay@cumulusnetworks.com
> Date: Fri, 24 Jul 2020 19:24:35 +0300
> 
> > While I agree this should have been done from the start, it's too late to change.   
> 
> Agreed.

Please fix the man page, the  usage and add a warning.

  reply	other threads:[~2020-07-26  3:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24 12:45 Bug in iproute2 man page (or in iproute itself) George Shuklin
2020-07-24 15:35 ` Stephen Hemminger
2020-07-24 16:15 ` [RFT iproute2] iplink_bridge: scale all time values by USER_HZ Stephen Hemminger
2020-07-24 16:24   ` nikolay
2020-07-24 19:05     ` Stephen Hemminger
2020-07-24 22:51       ` Nikolay Aleksandrov
2020-07-24 23:18         ` Vladimir Oltean
2020-07-25  0:31     ` David Miller
2020-07-26  3:17       ` Stephen Hemminger [this message]
2020-07-26 10:43         ` [RFC iproute2] ip: bridge: use -human to convert time-related values to seconds Nikolay Aleksandrov
2020-07-26 16:21           ` Vladimir Oltean
2020-07-26 16:34             ` Nikolay Aleksandrov
2020-07-26 16:50               ` Vladimir Oltean
2020-07-27 16:36                 ` Stephen Hemminger

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=20200725201758.4cfae512@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=amarao@servers.com \
    --cc=davem@davemloft.net \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.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).