Netdev List
 help / color / mirror / Atom feed
* [PATCH net-next v2 0/2] net: sgi: ioc3-eth: two changes for the IOC3 on SGI IP35 machines
@ 2026-11-16 10:21 Imre Kaloz
  2026-11-16 10:21 ` [PATCH net-next v2 1/2] net: sgi: ioc3-eth: apply the DMA attributes only to 64-bit addresses Imre Kaloz
  2026-11-16 10:21 ` [PATCH net-next v2 2/2] net: sgi: ioc3-eth: take the MAC address from a device property Imre Kaloz
  0 siblings, 2 replies; 5+ messages in thread
From: Imre Kaloz @ 2026-11-16 10:21 UTC (permalink / raw)
  To: Thomas Bogendoerfer, netdev
  Cc: Andrew Lunn, David S. Miller, Eric Dumazet, Jakub Kicinski,
	Paolo Abeni, linux-mips, linux-kernel

These two changes let ioc3-eth drive the IOC3 of the SGI Fuel, which
sits behind an XBridge and has no MAC PROM. They were part of the IP35
support series, which supplies the window addresses; its next version
attaches the MAC property. Neither side has a build dependency on the
other.

Tested on an SGI Fuel.

---
Changes in v2:
- Patch 2 takes the address from a device property instead of the
  platform hook, and drops the random address fallback.
- Patch 1's message no longer reads as a fix for existing systems.

v1: https://lore.kernel.org/all/20261111095138.1757-1-kaloz@kernel.org/

Imre Kaloz (2):
  net: sgi: ioc3-eth: apply the DMA attributes only to 64-bit addresses
  net: sgi: ioc3-eth: take the MAC address from a device property

 drivers/net/ethernet/sgi/ioc3-eth.c | 29 ++++++++++++++++++++++++-----
 1 file changed, 24 insertions(+), 5 deletions(-)


base-commit: 7ccc5e05043b1bb84326b19a2b05938d8f7a2ae6
-- 
2.47.3


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [PATCH net-next v2 1/2] net: sgi: ioc3-eth: apply the DMA attributes only to 64-bit addresses
  2026-11-16 10:21 [PATCH net-next v2 0/2] net: sgi: ioc3-eth: two changes for the IOC3 on SGI IP35 machines Imre Kaloz
@ 2026-11-16 10:21 ` Imre Kaloz
  2026-11-19 10:22   ` netdev-bot+sashiko
  2026-11-16 10:21 ` [PATCH net-next v2 2/2] net: sgi: ioc3-eth: take the MAC address from a device property Imre Kaloz
  1 sibling, 1 reply; 5+ messages in thread
From: Imre Kaloz @ 2026-11-16 10:21 UTC (permalink / raw)
  To: Thomas Bogendoerfer, netdev
  Cc: Andrew Lunn, David S. Miller, Eric Dumazet, Jakub Kicinski,
	Paolo Abeni, linux-mips, linux-kernel

A Bridge 32-bit direct window address carries no target widget, so
DMA attributes OR-ed onto it aim it at widget 0. IP27 and IP30 only
hand the IOC3 64-bit direct addresses; IP35 support will hand it
window addresses.

Signed-off-by: Imre Kaloz <kaloz@kernel.org>
---
 drivers/net/ethernet/sgi/ioc3-eth.c | 24 +++++++++++++++++++++---
 1 file changed, 21 insertions(+), 3 deletions(-)

diff --git a/drivers/net/ethernet/sgi/ioc3-eth.c b/drivers/net/ethernet/sgi/ioc3-eth.c
index 009f37105eaf..25139cf5ff62 100644
--- a/drivers/net/ethernet/sgi/ioc3-eth.c
+++ b/drivers/net/ethernet/sgi/ioc3-eth.c
@@ -152,19 +152,37 @@ static inline int ioc3_alloc_skb(struct ioc3_private *ip, struct sk_buff **skb,
 }
 
 #ifdef CONFIG_PCI_XTALK_BRIDGE
+/* A Bridge 64-bit direct-mapped DMA address carries the target widget in
+ * bits 63:60 and the DMA attributes below it.  An address in the 32-bit
+ * direct window carries neither, so attributes OR-ed onto one form a
+ * 64-bit address aimed at widget 0.
+ */
 static inline unsigned long ioc3_map(dma_addr_t addr, unsigned long attr)
 {
+	if (!(addr & PCI64_ATTR_TARG_MASK))
+		return addr;
+
 	return (addr & ~PCI64_ATTR_BAR) | attr;
 }
 
-#define ERBAR_VAL	(ERBAR_BARRIER_BIT << ERBAR_RXBARR_SHIFT)
+/* The RX barrier's upper address bits follow the same form. */
+static inline u32 ioc3_erbar(dma_addr_t addr)
+{
+	if (!(addr & PCI64_ATTR_TARG_MASK))
+		return 0;
+
+	return ERBAR_BARRIER_BIT << ERBAR_RXBARR_SHIFT;
+}
 #else
 static inline unsigned long ioc3_map(dma_addr_t addr, unsigned long attr)
 {
 	return addr;
 }
 
-#define ERBAR_VAL	0
+static inline u32 ioc3_erbar(dma_addr_t addr)
+{
+	return 0;
+}
 #endif
 
 static int ioc3eth_nvmem_match(struct device *dev, const void *data)
@@ -727,7 +745,7 @@ static void ioc3_init(struct net_device *dev)
 	readl(&regs->emcr);
 
 	/* Misc registers  */
-	writel(ERBAR_VAL, &regs->erbar);
+	writel(ioc3_erbar(ip->rxr_dma), &regs->erbar);
 	readl(&regs->etcdc);			/* Clear on read */
 	writel(15, &regs->ercsr);		/* RX low watermark  */
 	writel(0, &regs->ertr);			/* Interrupt immediately */
-- 
2.47.3


^ permalink raw reply related	[flat|nested] 5+ messages in thread

* [PATCH net-next v2 2/2] net: sgi: ioc3-eth: take the MAC address from a device property
  2026-11-16 10:21 [PATCH net-next v2 0/2] net: sgi: ioc3-eth: two changes for the IOC3 on SGI IP35 machines Imre Kaloz
  2026-11-16 10:21 ` [PATCH net-next v2 1/2] net: sgi: ioc3-eth: apply the DMA attributes only to 64-bit addresses Imre Kaloz
@ 2026-11-16 10:21 ` Imre Kaloz
  2026-11-19 10:22   ` netdev-bot+sashiko
  1 sibling, 1 reply; 5+ messages in thread
From: Imre Kaloz @ 2026-11-16 10:21 UTC (permalink / raw)
  To: Thomas Bogendoerfer, netdev
  Cc: Andrew Lunn, David S. Miller, Eric Dumazet, Jakub Kicinski,
	Paolo Abeni, linux-mips, linux-kernel

Some boards have no MAC PROM on the IOC3's 1-wire bus, and the probe
defers forever there. Let the platform supply the address as a device
property for such a board.

Signed-off-by: Imre Kaloz <kaloz@kernel.org>
---
 drivers/net/ethernet/sgi/ioc3-eth.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/drivers/net/ethernet/sgi/ioc3-eth.c b/drivers/net/ethernet/sgi/ioc3-eth.c
index 25139cf5ff62..fa844267c325 100644
--- a/drivers/net/ethernet/sgi/ioc3-eth.c
+++ b/drivers/net/ethernet/sgi/ioc3-eth.c
@@ -857,8 +857,9 @@ static int ioc3eth_probe(struct platform_device *pdev)
 		dev_err(&pdev->dev, "Invalid resource\n");
 		return -EINVAL;
 	}
-	/* get mac addr from one wire prom */
-	if (ioc3eth_get_mac_addr(regs, mac_addr))
+	/* get mac addr from one wire prom, or from a device property */
+	if (ioc3eth_get_mac_addr(regs, mac_addr) &&
+	    device_get_mac_address(&pdev->dev, mac_addr))
 		return -EPROBE_DEFER; /* not available yet */
 
 	dev = alloc_etherdev(sizeof(struct ioc3_private));
-- 
2.47.3


^ permalink raw reply related	[flat|nested] 5+ messages in thread

* Re: [PATCH net-next v2 1/2] net: sgi: ioc3-eth: apply the DMA attributes only to 64-bit addresses
  2026-11-16 10:21 ` [PATCH net-next v2 1/2] net: sgi: ioc3-eth: apply the DMA attributes only to 64-bit addresses Imre Kaloz
@ 2026-11-19 10:22   ` netdev-bot+sashiko
  0 siblings, 0 replies; 5+ messages in thread
From: netdev-bot+sashiko @ 2026-11-19 10:22 UTC (permalink / raw)
  To: kaloz
  Cc: tsbogend, netdev, andrew+netdev, davem, edumazet, kuba, pabeni,
	linux-mips, linux-kernel

Thank you for your contribution! Sashiko AI review found 1 potential
issue(s) to consider.

Critical: 0 · High: 0 (1) · Medium: 1 · Low: 0

If you believe none of the issues are legitimate, please reply to each
issue of Medium severity or higher and explain why the AI is wrong.
If any of them are legitimate and you plan to respin, please let patchwork
know by including "pw-bot: cr" as a separate line at the end of your reply
(one such reply per series is enough).

- [Medium] On 32-bit direct-window DMA addresses, the new helpers drop
  all Bridge DMA attributes, and nothing provides them another way.

Pre-existing issues:
- [High] This problem wasn't introduced by this patch, but it is in
  ioc3_init(), the function the patch changes.

--

net: sgi: ioc3-eth: apply the DMA attributes only to 64-bit addresses

This commit changes ioc3_map() so it leaves out the Bridge DMA attributes
when the DMA address has no target widget in bits 63:60, which is the case
for a 32-bit direct window address. It also replaces ERBAR_VAL with
ioc3_erbar(), which returns 0 for such addresses. ioc3_init() now picks
the ERBAR value from the RX ring DMA address. The goal is to prepare for
IP35 support, which will give the IOC3 window addresses.

> diff --git a/drivers/net/ethernet/sgi/ioc3-eth.c b/drivers/net/ethernet/sgi/ioc3-eth.c
> index 009f37105eafd..25139cf5ff62c 100644
> --- a/drivers/net/ethernet/sgi/ioc3-eth.c
> +++ b/drivers/net/ethernet/sgi/ioc3-eth.c
> @@ -152,19 +152,37 @@ static inline int ioc3_alloc_skb(struct ioc3_private *ip, struct sk_buff **skb,
>  }
>  
>  #ifdef CONFIG_PCI_XTALK_BRIDGE
> +/* A Bridge 64-bit direct-mapped DMA address carries the target widget in
> + * bits 63:60 and the DMA attributes below it.  An address in the 32-bit
> + * direct window carries neither, so attributes OR-ed onto one form a
> + * 64-bit address aimed at widget 0.
> + */
>  static inline unsigned long ioc3_map(dma_addr_t addr, unsigned long attr)
>  {
> +	if (!(addr & PCI64_ATTR_TARG_MASK))
> +		return addr;
> +
>  	return (addr & ~PCI64_ATTR_BAR) | attr;
>  }
>  
> -#define ERBAR_VAL	(ERBAR_BARRIER_BIT << ERBAR_RXBARR_SHIFT)
> +/* The RX barrier's upper address bits follow the same form. */
> +static inline u32 ioc3_erbar(dma_addr_t addr)
> +{
> +	if (!(addr & PCI64_ATTR_TARG_MASK))
> +		return 0;
> +
> +	return ERBAR_BARRIER_BIT << ERBAR_RXBARR_SHIFT;
> +}

[Severity: Medium]

For a 32-bit direct window address, ioc3_map() now returns the bare
address and ioc3_erbar() returns 0. Where do the dropped attributes come
from in that case?

Three attributes are lost. ioc3_rx() and ioc3_alloc_rx_bufs() lose
PCI64_ATTR_BAR on the RX buffer pointers. ioc3_start() loses
PCI64_ATTR_PREC on the ring bases. ioc3_start_xmit() loses PCI64_ATTR_PREF
on the TX buffer pointers.

For 32-bit direct DMA the Bridge takes these from the per-slot Device(x)
register (BRIDGE_DEV_PREF, BRIDGE_DEV_PRECISE and BRIDGE_DEV_BARRIER in
BRIDGE_DEV_D32_BITS). The only code in the tree that writes
b_device[slot] is bridge_probe(), and it sets only the swap bit:

arch/mips/pci/pci-xtalk-bridge.c:bridge_probe() {
    ...
		bridge_set(bc, b_device[slot].reg, BRIDGE_DEV_SWAP_DIR);
    ...
}

ERBAR is now 0 as well. What, then, orders the ERXBUF w0 valid-word store
after the payload stores? ioc3_rx() trusts that word before it reads the
frame:

	while (w0 & ERXBUF_V) {
		err = be32_to_cpu(rxb->err);		/* It's valid ...  */

Could the CPU see ERXBUF_V before the payload has landed, and pass a stale
or truncated frame up the stack?

There is a separate question about ioc3_init(), which picks the ERBAR
value from the coherent ring address:

	writel(ioc3_erbar(ip->rxr_dma), &regs->erbar);

ERBAR applies to the last store into each RX buffer. Those buffers are
separate streaming mappings from ioc3_alloc_skb(). ioc3_map() decides per
address, so suppose the ring gets a 64-bit address and an RX buffer gets a
window address. Wouldn't ERBAR still OR the barrier attribute into the
upper bits of that buffer's last store, which gives the widget 0 address
this patch is meant to avoid? This assumes the IOC3 ORs ERBAR onto the
upper address bits.

None of this can be reached on in-tree platforms. phys_to_dma() returns
bc->baddr + paddr, and baddr has a non-zero target nibble on both IP27 and
IP30. Whether it triggers depends on how the IP35 support maps DMA and
programs Device(x).

The commit message also doesn't say that the RX barrier is turned off for
window addresses, or what replaces it. Could that be added?

>  #else
>  static inline unsigned long ioc3_map(dma_addr_t addr, unsigned long attr)
>  {

[ ... ]

> @@ -727,7 +745,7 @@ static void ioc3_init(struct net_device *dev)
>  	readl(&regs->emcr);
>  
>  	/* Misc registers  */
> -	writel(ERBAR_VAL, &regs->erbar);
> +	writel(ioc3_erbar(ip->rxr_dma), &regs->erbar);

[Severity: High]

This isn't a bug introduced by this patch, but ioc3_init() starts with a
synchronous timer delete, and both error-recovery callers hold
ip->ioc3_lock when they call it:

ioc3_init() {
	timer_delete_sync(&ip->ioc3_timer);	/* Kill if running	*/
	...
}

ioc3_error() runs from the hardirq handler ioc3_interrupt() and does:

	spin_lock(&ip->ioc3_lock);
	...
	ioc3_init(dev);

ioc3_timeout() does the same thing with spin_lock_irq(). The timer
callback takes the same lock:

ioc3_timer()
  mii_check_media()
  ioc3_setup_duplex()
    spin_lock_irq(&ip->ioc3_lock);

Can this deadlock on SMP?

CPU A
ioc3_timer()
  ioc3_setup_duplex()
    spin_lock_irq(&ip->ioc3_lock)    <- spins on the lock CPU B holds

CPU B
ioc3_error() or ioc3_timeout()
  spin_lock(&ip->ioc3_lock)
  ioc3_init()
    timer_delete_sync()              <- waits for CPU A's callback

Also, ioc3eth_probe() sets up the timer without TIMER_IRQSAFE:

	timer_setup(&ip->ioc3_timer, ioc3_timer, 0);

So won't every hardirq call through ioc3_error() hit this check in
__timer_delete_sync()?

	WARN_ON(in_hardirq() && !(timer->flags & TIMER_IRQSAFE));

ioc3_error() runs on EISR_RXOFLO or EISR_RXBUFOFLO, so incoming traffic
that outruns the RX ring is enough to trigger it.

Last, ioc3_error() calls ioc3_mii_init() but not ioc3_mii_start(), unlike
ioc3_timeout(). If the timer is never re-armed, does link and duplex
monitoring stop after an error recovery?

>  	readl(&regs->etcdc);			/* Clear on read */
>  	writel(15, &regs->ercsr);		/* RX low watermark  */
>  	writel(0, &regs->ertr);			/* Interrupt immediately */

-- 
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261116102115.27574-1-kaloz%40kernel.org

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH net-next v2 2/2] net: sgi: ioc3-eth: take the MAC address from a device property
  2026-11-16 10:21 ` [PATCH net-next v2 2/2] net: sgi: ioc3-eth: take the MAC address from a device property Imre Kaloz
@ 2026-11-19 10:22   ` netdev-bot+sashiko
  0 siblings, 0 replies; 5+ messages in thread
From: netdev-bot+sashiko @ 2026-11-19 10:22 UTC (permalink / raw)
  To: kaloz
  Cc: tsbogend, netdev, andrew+netdev, davem, edumazet, kuba, pabeni,
	linux-mips, linux-kernel

Thank you for your contribution! Sashiko AI review found 2 potential
issue(s) to consider.

Critical: 0 · High: 0 (2) · Medium: 2 · Low: 0

If you believe none of the issues are legitimate, please reply to each
issue of Medium severity or higher and explain why the AI is wrong.
If any of them are legitimate and you plan to respin, please let patchwork
know by including "pw-bot: cr" as a separate line at the end of your reply
(one such reply per series is enough).

- [Medium] The new fallback in ioc3eth_probe()
  (drivers/net/ethernet/sgi/ioc3-eth.c:861-863) calls…
- [Medium] On a board that has a 1-wire MAC PROM and also gets the new
  device property, which MAC address ioc3eth_probe() uses depends on…

Pre-existing issues:
- [High] This problem wasn't introduced by this patch, but
  ioc3eth_probe() never calls platform_set_drvdata(pdev, dev), while…
- [High] This problem wasn't introduced by this patch, but
  ioc3eth_probe() requests the IRQ with devm_request_irq(&pdev->dev,…

--

net: sgi: ioc3-eth: take the MAC address from a device property

This commit adds a device_get_mac_address() fallback to ioc3eth_probe().
It is used when the MAC address can't be read from the 1-wire PROM, so
that boards without a PROM no longer defer probing forever.

> diff --git a/drivers/net/ethernet/sgi/ioc3-eth.c b/drivers/net/ethernet/sgi/ioc3-eth.c
> index 25139cf5ff62c..fa844267c325a 100644
> --- a/drivers/net/ethernet/sgi/ioc3-eth.c
> +++ b/drivers/net/ethernet/sgi/ioc3-eth.c
> @@ -857,8 +857,9 @@ static int ioc3eth_probe(struct platform_device *pdev)
>  		dev_err(&pdev->dev, "Invalid resource\n");
>  		return -EINVAL;
>  	}
> -	/* get mac addr from one wire prom */
> -	if (ioc3eth_get_mac_addr(regs, mac_addr))
> +	/* get mac addr from one wire prom, or from a device property */
> +	if (ioc3eth_get_mac_addr(regs, mac_addr) &&
> +	    device_get_mac_address(&pdev->dev, mac_addr))

[Severity: Medium]
Can device_get_mac_address() succeed for this device on any in-tree board?

Only ioc3_eth_setup() in drivers/mfd/ioc3.c creates the ioc3-eth platform
device, and it does so from this cell:

drivers/mfd/ioc3.c:
static struct mfd_cell ioc3_eth_cells[] = {
	{
		.name = "ioc3-eth",
		.resources = ioc3_eth_resources,
		.num_resources = ARRAY_SIZE(ioc3_eth_resources),
	},

The cell sets neither .swnode nor .of_compatible, and IP27/IP30 have no
DT or ACPI. So mfd_add_device() never gives the child a fwnode.
dev_fwnode() returns NULL and fwnode_get_mac_address() fails.

The second step, nvmem_get_mac_address(), ends up in
nvmem_cell_get_from_lookup(), which is keyed by dev_name(). The child is
registered with PLATFORM_DEVID_AUTO ("ioc3-eth.N.auto"), so board code
can't target it reliably. Nothing in tree registers such a lookup either.

As far as I can tell, boards without a 1-wire MAC PROM still defer
forever, which is the problem the commit message says this fixes.

Which board is this meant for? Is there a companion change to
drivers/mfd/ioc3.c, for example a software node with "mac-address" or
"local-mac-address" attached to the ioc3-eth cell?

The previous commit in the series mentions "IP35 support will hand it
window addresses", so the user may be out of tree or not posted yet. Could
the commit message say so?

[Severity: Medium]
What happens on a board that has the 1-wire PROM and also gets the
property?

ioc3eth_get_mac_addr() passes the nvmem_device_find() error through
unchanged:

	nvmem = nvmem_device_find(prefix, ioc3eth_nvmem_match);
	if (IS_ERR(nvmem))
		return PTR_ERR(nvmem);

nvmem_device_match() in drivers/nvmem/core.c returns
ERR_PTR(-EPROBE_DEFER) whenever the PROM's nvmem device isn't registered
yet. So "no PROM fitted" and "PROM not enumerated yet" give the same
error here.

The PROM's nvmem device only appears after the w1 master kthread
(w1_process()->w1_search_process()) finds the slave and the family driver
binds. Also, the "ioc3-eth" cell comes before "sgi_w1" in
ioc3_eth_cells[], so the first ioc3-eth probe can run before the 1-wire
master exists at all.

Before this patch, any PROM failure deferred the probe, so a board with a
PROM always ended up using the PROM address. Now the first failed lookup
falls back to the property and probe succeeds. eth_hw_addr_set() and
ioc3_init() then program that address into EMAR_H/EMAR_L for the rest of
the boot.

Could the MAC address then change from boot to boot, depending on w1
enumeration timing? The new comment suggests the PROM takes priority, but
that only holds if enumeration finishes first.

A PROM with a bad CRC (-EINVAL) also falls back to the property without
any message, and nothing logs which source supplied the address.

>  		return -EPROBE_DEFER; /* not available yet */
>  
>  	dev = alloc_etherdev(sizeof(struct ioc3_private));

[Severity: High]
This isn't a bug introduced by this patch, but ioc3eth_probe() never calls
platform_set_drvdata(pdev, dev), while ioc3eth_remove() relies on it:

drivers/net/ethernet/sgi/ioc3-eth.c:ioc3eth_remove() {
	struct net_device *dev = platform_get_drvdata(pdev);
	struct ioc3_private *ip = netdev_priv(dev);

	unregister_netdev(dev);
	timer_delete_sync(&ip->ioc3_timer);
	...
}

After a successful probe, won't platform_get_drvdata() return NULL here?
If so, unregister_netdev(NULL) oopses. The timer_delete_sync() and
dma_free_coherent() calls would then work on a bogus ip pointer, and the
netdev, DMA rings and timer never get torn down.

This path is reachable through /sys/bus/platform/drivers/ioc3-eth/unbind
(suppress_bind_attrs isn't set), or by removing the parent IOC3 MFD
device.

Because this patch lets probe succeed on more boards, more systems can
reach this remove path.

[Severity: High]
This is also a pre-existing issue, but ioc3eth_probe() requests a shared
IRQ with devm and passes the net_device, which isn't devm-managed, as
dev_id:

	if (devm_request_irq(&pdev->dev, dev->irq, ioc3_interrupt,
			     IRQF_SHARED, "ioc3-eth", dev)) {

Every error path after that ends here: rx/tx ring allocation failure, the
"Didn't find a PHY" case, and register_netdev() failure.

out_free:
	free_netdev(dev);
	return err;

The netdev was never registered, so free_netdev() frees it right away.
The IRQ stays installed until devres_release_all() runs after probe
returns. ioc3eth_remove() has the same ordering: it calls free_netdev(dev)
before devres frees the IRQ.

Can ioc3_interrupt() run on the freed net_device in that window?

static irqreturn_t ioc3_interrupt(int irq, void *dev_id)
{
	struct ioc3_private *ip = netdev_priv(dev_id);
	struct ioc3_ethregs *regs = ip->regs;
	u32 eisr;

	eisr = readl(&regs->eisr);
	writel(eisr, &regs->eisr);
	...

An interrupt from another device on the shared line can trigger this.
With CONFIG_DEBUG_SHIRQ it always happens, because __free_irq() calls the
handler one extra time for IRQF_SHARED actions.

Either a plain request_irq()/free_irq() pair, with free_irq() called
before free_netdev(), or devm_alloc_etherdev() would avoid this.

-- 
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261116102115.27574-1-kaloz%40kernel.org

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2026-11-19 10:22 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-16 10:21 [PATCH net-next v2 0/2] net: sgi: ioc3-eth: two changes for the IOC3 on SGI IP35 machines Imre Kaloz
2026-11-16 10:21 ` [PATCH net-next v2 1/2] net: sgi: ioc3-eth: apply the DMA attributes only to 64-bit addresses Imre Kaloz
2026-11-19 10:22   ` netdev-bot+sashiko
2026-11-16 10:21 ` [PATCH net-next v2 2/2] net: sgi: ioc3-eth: take the MAC address from a device property Imre Kaloz
2026-11-19 10:22   ` netdev-bot+sashiko

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox