All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Harry Coin <hcoin@quietfountain.com>,
	Kuniyuki Iwashima <kuniyu@amazon.com>,
	netdev@vger.kernel.org
Subject: Re: llc needs namespace awareness asap, was Re: Patch fixing STP if bridge in non-default namespace.
Date: Tue, 11 Jul 2023 17:49:34 -0700	[thread overview]
Message-ID: <20230711174934.3871fb61@kernel.org> (raw)
In-Reply-To: <cacc74f8-5b40-4d89-a411-a6852ea60e7d@lunn.ch>

On Tue, 11 Jul 2023 22:44:44 +0200 Andrew Lunn wrote:
> o It cannot be bigger than 100 lines, with context.

Let's take stable rules with a large pinch of salt.
None of them are hard rules, especially the 100 line one.

  parent reply	other threads:[~2023-07-12  0:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 13:35 Patch fixing STP if bridge in non-default namespace Harry Coin
2023-07-11  3:22 ` Kuniyuki Iwashima
2023-07-11 17:08   ` llc needs namespace awareness asap, was " Harry Coin
2023-07-11 18:32     ` Kuniyuki Iwashima
2023-07-11 20:22       ` Harry Coin
2023-07-11 20:44         ` Andrew Lunn
2023-07-11 21:40           ` Harry Coin
2023-07-11 21:51             ` Kuniyuki Iwashima
2023-07-11 22:44               ` Harry Coin
2023-07-11 22:56                 ` Kuniyuki Iwashima
     [not found]               ` <b01e5af6-e397-486d-3428-6fa30a919042@quietfountain.com>
2023-07-12  0:55                 ` Andrew Lunn
2023-07-12  3:06                   ` Harry Coin
2023-07-13 22:37                     ` Stephen Hemminger
2023-07-12  9:44               ` [Bridge] " Petr Machata
2023-07-12  9:44                 ` Petr Machata
2023-07-12  0:49           ` Jakub Kicinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-02  3:45 Hasenbosch, Samuel J
2023-08-02  3:50 ` Kuniyuki Iwashima

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=20230711174934.3871fb61@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=hcoin@quietfountain.com \
    --cc=kuniyu@amazon.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.