All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Jiri Benc <jbenc@redhat.com>
Cc: Jakub Kicinski <kubakici@wp.pl>, Ido Schimmel <idosch@idosch.org>,
	Ido Schimmel <idosch@mellanox.com>,
	netdev@vger.kernel.org, davem@davemloft.net, jiri@mellanox.com,
	dsahern@gmail.com, mlxsw@mellanox.com
Subject: Re: [PATCH net-next] team: Use extack to report enslavement failures
Date: Wed, 28 Feb 2018 10:29:07 +0100	[thread overview]
Message-ID: <20180228092907.GD19654@nanopsycho> (raw)
In-Reply-To: <20180228095803.4318f57c@redhat.com>

Wed, Feb 28, 2018 at 09:58:03AM CET, jbenc@redhat.com wrote:
>On Wed, 28 Feb 2018 08:12:41 +0100, Jiri Pirko wrote:
>> Yeah, or if you have an older iproute2 package. I would keep the existing
>> dmesg msgs for now. In the future, when everyone is used to exacks, then
>> we can remove them.
>
>How do we ensure that this will actually happen in the future? Usually,
>when not done right away, such things tend to be forgotten for years or
>even forever.
>
>Also, how distant future are we talking about?

I would say, quite distant :)
On the other hand, I don't care much about this in particular.

  reply	other threads:[~2018-02-28  9:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 15:38 [PATCH net-next] team: Use extack to report enslavement failures Ido Schimmel
2018-02-27 16:37 ` David Ahern
2018-02-27 19:42 ` Jiri Benc
2018-02-27 20:22   ` Ido Schimmel
2018-02-27 23:49     ` Jakub Kicinski
2018-02-28  7:12       ` Jiri Pirko
2018-02-28  7:21         ` Yuval Mintz
2018-02-28  8:58         ` Jiri Benc
2018-02-28  9:29           ` Jiri Pirko [this message]
2018-02-28 14:28         ` David Miller
2018-02-28 16:02 ` 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=20180228092907.GD19654@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=idosch@idosch.org \
    --cc=idosch@mellanox.com \
    --cc=jbenc@redhat.com \
    --cc=jiri@mellanox.com \
    --cc=kubakici@wp.pl \
    --cc=mlxsw@mellanox.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.