netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Luiz Angelo Daros de Luca <luizluca@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: dsa: tag_rtl4_a: Bump min packet size
Date: Thu, 2 Nov 2023 12:45:50 +0200	[thread overview]
Message-ID: <20231102104550.iuw5ozfchbm3u667@skbuf> (raw)
In-Reply-To: <CACRpkdaoBo0S0RgLhacObd3pbjtWAfr6s3oizQAHqdB76gaG5A@mail.gmail.com>

On Wed, Nov 01, 2023 at 09:26:50PM +0100, Linus Walleij wrote:
> On Wed, Nov 1, 2023 at 1:35 PM Luiz Angelo Daros de Luca <luizluca@gmail.com> wrote:
> 
> > Sorry but I noticed no issues:
> 
> Don't be sorry about that, it's good news because now I know
> where to look, i.e. in the ethernet controller.

Don't look too deeply into the code just yet, just try to see what
happens with dsa_loop on an identical Ethernet controller that isn't
physically attached to a switch.

  parent reply	other threads:[~2023-11-02 10:45 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30  9:26 [PATCH net v2] net: dsa: tag_rtl4_a: Bump min packet size Linus Walleij
2023-10-30 14:16 ` Vladimir Oltean
2023-10-30 14:37   ` Linus Walleij
2023-10-30 15:23     ` Vladimir Oltean
2023-10-30 15:30       ` Vladimir Oltean
2023-10-31 21:22         ` Linus Walleij
2023-11-02 10:48           ` Vladimir Oltean
2023-10-30 21:50   ` Linus Walleij
2023-10-30 22:20     ` Vladimir Oltean
2023-10-30 22:57       ` Linus Walleij
2023-10-30 23:09         ` Vladimir Oltean
2023-10-30 23:11           ` Linus Walleij
2023-10-31  0:37           ` Andrew Lunn
2023-10-31  3:37             ` Florian Fainelli
2023-10-31 14:06             ` Linus Walleij
2023-10-31 16:23               ` Florian Fainelli
2023-10-30 23:33         ` Vladimir Oltean
2023-10-31 14:16           ` Linus Walleij
2023-10-31 16:34             ` Vladimir Oltean
2023-10-31 19:02               ` Linus Walleij
2023-11-02 12:32                 ` Vladimir Oltean
2023-10-31 19:18             ` Luiz Angelo Daros de Luca
2023-10-31 19:27               ` Linus Walleij
2023-11-01 12:35                 ` Luiz Angelo Daros de Luca
2023-11-01 20:26                   ` Linus Walleij
2023-11-02 10:04                     ` Vladimir Oltean
2023-11-02 10:45                     ` Vladimir Oltean [this message]
2023-11-03 17:05                     ` Luiz Angelo Daros de Luca
2023-12-30  5:19                     ` Luiz Angelo Daros de Luca
2023-12-30 12:28                       ` Linus Walleij
2023-12-30 23:56                         ` Luiz Angelo Daros de Luca
2023-11-02 10:31                   ` Vladimir Oltean
2023-11-03 17:13                     ` Luiz Angelo Daros de Luca
2023-10-31 22:44   ` Linus Walleij

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=20231102104550.iuw5ozfchbm3u667@skbuf \
    --to=olteanv@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luizluca@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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).