linux-kernel - Re: [PATCH 0/3] Fix EEE support for MT7531 and MT7988 SoC switch

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240319-uppish-idealistic-giraffe-e17cb4@lemur>
Date: Tue, 19 Mar 2024 12:03:15 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Arınç ÜNAL <arinc.unal@...nc9.com>
Cc: Florian Fainelli <f.fainelli@...il.com>, 
	Daniel Golle <daniel@...rotopia.org>, DENG Qingfang <dqfext@...il.com>, 
	Sean Wang <sean.wang@...iatek.com>, Andrew Lunn <andrew@...n.ch>, 
	Vladimir Oltean <olteanv@...il.com>, "David S. Miller" <davem@...emloft.net>, 
	Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, 
	Paolo Abeni <pabeni@...hat.com>, Matthias Brugger <matthias.bgg@...il.com>, 
	AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>, René van Dorst <opensource@...rst.com>, 
	Russell King <linux@...linux.org.uk>, SkyLake Huang <SkyLake.Huang@...iatek.com>, 
	Heiner Kallweit <hkallweit1@...il.com>, Bartel Eerdekens <bartel.eerdekens@...stell8.be>, 
	mithat.guner@...ont.com, erkin.bozoglu@...ont.com, netdev@...r.kernel.org, 
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
	linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH 0/3] Fix EEE support for MT7531 and MT7988 SoC switch

On Mon, Mar 18, 2024 at 02:01:58PM -0400, Konstantin Ryabitsev wrote:
> > It looks like my branch name was too long again. b4 0.13.0 cannot handle
> > branch names that are too long. I'll keep it shorter for future
> > submissions. It'd be great if Konstantin could provide a specific limit.
> 
> It's not really b4, it's the web endpoint and the version of python it's
> running. I hope to fix it soon by applying the same workarounds as we ended up
> doing for b4 itself.

I've deployed the version of endpoint that works around this bug. Hopefully,
you won't see it again regardless of the message-id length.

-K