All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: 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 14:32:30 +0200	[thread overview]
Message-ID: <20231102123230.luoyrh2j4r4bbwjf@skbuf> (raw)
In-Reply-To: <CACRpkdb=16uLhsXhktLCwUByDAMv9Arg2zzCA+oJW2HBJ35-Bg@mail.gmail.com>

On Tue, Oct 31, 2023 at 08:02:29PM +0100, Linus Walleij wrote:
> On Tue, Oct 31, 2023 at 5:34 PM Vladimir Oltean <olteanv@gmail.com> wrote:
> > So on the gemini-dlink-dir-685.dts platform, you can also use &gmac1 as
> > a plain Ethernet port, right?
> 
> As a port it exist on the SoC yes but it is not connected physically
> to anything.
> 
> &gmac0 is connected to the switch, and the switch has all the PHYs.
(...)
> If you by remote end mean the end of a physical cable there is
> no way I can do that, as I have no PHY on gmac1.
> 
> (I don't know if I misunderstand the question...)

No, you aren't.

> But I have other Gemini platforms, so I will try to do it on one
> of them! Let's see if I can do this thing....

Ok.

  reply	other threads:[~2023-11-02 12:32 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 [this message]
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
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=20231102123230.luoyrh2j4r4bbwjf@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=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 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.