All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Jakub Kicinski <kuba@kernel.org>,
	Alexander Duyck <alexander.duyck@gmail.com>,
	netdev@vger.kernel.org, hkallweit1@gmail.com,
	davem@davemloft.net, pabeni@redhat.com
Subject: Re: [net-next PATCH 0/2] net: phylink: Fix issue w/ BMC link flap
Date: Tue, 22 Apr 2025 19:50:19 +0100	[thread overview]
Message-ID: <aAfk662jTFj4iIQD@shell.armlinux.org.uk> (raw)
In-Reply-To: <e7815c91-e047-4b3e-b3e4-371f30c9dadd@lunn.ch>

On Tue, Apr 22, 2025 at 08:13:43PM +0200, Andrew Lunn wrote:
> > Should one host have control, or should the BMC have control? I don't
> > actually know what you're talking about w.r.t. DSP0222 or whatever it
> > was, nor NC-SI - I don't have these documents.
> 
> I gave a reference to it a few email back in the conversation:
> 
> https://www.dmtf.org/sites/default/files/standards/documents/DSP0222_1.2.0.pdf
> 
> Linux has an implementation of the protocol in net/nsci

Hmm. I don't think I have bandwidth to read that spec any time soon,
sorry.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2025-04-22 18:50 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16 15:28 [net-next PATCH 0/2] net: phylink: Fix issue w/ BMC link flap Alexander Duyck
2025-04-16 15:28 ` [net-next PATCH 1/2] net: phylink: Drop unused defines for SUPPORTED/ADVERTISED_INTERFACES Alexander Duyck
2025-04-22  8:32   ` Russell King (Oracle)
2025-04-16 15:29 ` [net-next PATCH 2/2] net: phylink: Fix issues with link balancing w/ BMC present Alexander Duyck
2025-04-16 16:01   ` Russell King (Oracle)
2025-04-16 16:16     ` [PATCH net] net: phylink: fix suspend/resume with WoL enabled and link down Russell King (Oracle)
2025-04-16 17:14       ` Russell King (Oracle)
2025-04-17 14:30       ` Alexander H Duyck
2025-04-17 14:35         ` Russell King (Oracle)
2025-04-17 15:23           ` Russell King (Oracle)
2025-04-17 17:06             ` Alexander Duyck
2025-04-17 17:27               ` Russell King (Oracle)
2025-04-17 19:49                 ` Alexander Duyck
2025-04-22  9:51                   ` Russell King (Oracle)
2025-04-22 15:30                     ` Alexander Duyck
2025-04-22 16:00                       ` Andrew Lunn
2025-04-22 20:09                         ` Alexander Duyck
2025-04-23  0:00       ` patchwork-bot+netdevbpf
2025-04-16 17:12     ` [net-next PATCH 2/2] net: phylink: Fix issues with link balancing w/ BMC present Russell King (Oracle)
2025-04-16 19:03     ` Alexander Duyck
2025-04-16 19:19       ` Russell King (Oracle)
2025-04-16 20:05         ` Russell King (Oracle)
2025-04-16 22:58           ` Alexander Duyck
2025-04-19 18:11 ` [net-next PATCH 0/2] net: phylink: Fix issue w/ BMC link flap Andrew Lunn
2025-04-20 18:18   ` Alexander Duyck
2025-04-20 21:58     ` Andrew Lunn
2025-04-21 15:51       ` Alexander Duyck
2025-04-21 16:50         ` Alexander Duyck
2025-04-22  1:21           ` Jakub Kicinski
2025-04-22 13:49             ` Andrew Lunn
2025-04-22 15:28               ` Jakub Kicinski
2025-04-22 16:49                 ` Andrew Lunn
2025-04-22 17:30                   ` Russell King (Oracle)
2025-04-22 18:13                     ` Andrew Lunn
2025-04-22 18:50                       ` Russell King (Oracle) [this message]
2025-04-22 23:51                       ` Jakub Kicinski
2025-04-22 21:29                   ` Alexander Duyck
2025-04-22 22:26                     ` Andrew Lunn
2025-04-22 23:06                       ` Alexander Duyck
2025-04-23 18:38                         ` Alexander Duyck
2025-04-24 20:34                         ` Andrew Lunn
2025-04-24 23:40                           ` Alexander Duyck
2025-04-25 13:11                             ` Andrew Lunn
2025-04-25 15:41                               ` Alexander Duyck

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=aAfk662jTFj4iIQD@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=alexander.duyck@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@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.