lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 13 Nov 2020 11:54:26 -0800 From: Jakub Kicinski <kuba@...nel.org> To: Ioana Ciornei <ioana.ciornei@....com> Cc: Ioana Ciornei <ciorneiioana@...il.com>, Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>, Russell King <linux@...linux.org.uk>, Florian Fainelli <f.fainelli@...il.com>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Alexandru Ardelean <alexandru.ardelean@...log.com>, Andre Edich <andre.edich@...rochip.com>, Baruch Siach <baruch@...s.co.il>, Christophe Leroy <christophe.leroy@....fr>, Kavya Sree Kotagiri <kavyasree.kotagiri@...rochip.com>, Linus Walleij <linus.walleij@...aro.org>, Marco Felsch <m.felsch@...gutronix.de>, Marek Vasut <marex@...x.de>, Maxim Kochetkov <fido_max@...ox.ru>, Nisar Sayed <Nisar.Sayed@...rochip.com>, Oleksij Rempel <o.rempel@...gutronix.de>, Robert Hancock <robert.hancock@...ian.com>, Yuiko Oshino <yuiko.oshino@...rochip.com> Subject: Re: [PATCH net-next 00/18] net: phy: add support for shared interrupts (part 2) On Fri, 13 Nov 2020 08:17:00 +0000 Ioana Ciornei wrote: > On Thu, Nov 12, 2020 at 06:19:10PM -0800, Jakub Kicinski wrote: > > On Thu, 12 Nov 2020 17:54:55 +0200 Ioana Ciornei wrote: > > > From: Ioana Ciornei <ioana.ciornei@....com> > > > > > > This patch set aims to actually add support for shared interrupts in > > > phylib and not only for multi-PHY devices. While we are at it, > > > streamline the interrupt handling in phylib. > > > > Ioana, would you mind resending? Looks like the kernel.org patchwork > > instance is way less reliable at piecing series together :( > > No problem, I'll resend. > > So from now on we'll be using the kernel.org patchwork only, right? I > am asking this because from what I can tell the ozlabs patchwork was not > updated in the last days. Yup, that's the plan. We're keeping ozlabs going for a bit just in case kernel.org is acting up (like if the need to repost stuff persists), but the plan is to stop the patchwork entry for netdev on ozlabs once things settle. From where I live ozlabs takes 1s to respond to a request while kernel.org instance takes 0.2s.
Powered by blists - more mailing lists