| 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
| ||
|
Message-ID: <e843b3f9-2214-4945-bc07-68fe935551a5@csgroup.eu> Date: Thu, 3 Oct 2024 18:08:30 +0200 From: Christophe Leroy <christophe.leroy@...roup.eu> To: Markus Elfring <Markus.Elfring@....de>, kernel-janitors@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org, Benjamin Herrenschmidt <benh@...nel.crashing.org>, Josh Boyer <jwboyer@...ux.vnet.ibm.com>, Michael Ellerman <mpe@...erman.id.au>, Nicholas Piggin <npiggin@...il.com>, Stefan Roese <sr@...x.de> Cc: cocci@...ia.fr, LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v2 1/4] powerpc/4xx: Fix exception handling in ppc4xx_pciex_port_setup_hose() Le 03/10/2024 à 17:47, Markus Elfring a écrit : > … >> Looks like you have messed up your patches, > > There were special communication settings involved which hindered desirable > data processing for known information systems. Don't know what you mean. > > >> there is no much we can do it seems: >> >> $ b4 shazam e68a714b-32f2-de9f-066e-99a3f51a264f@....de > > Please take another look also at published information according to further > mailing list archive interfaces. Another look to what ? It seems like several patches were posted with the same Message-Id and/or with an unrelated In-Reply-To: b4 is lost and cannot apply your series, it applies the patch at https://lore.kernel.org/all/82aebf6c-47ac-9d17-2d11-6245f582338e@web.de/ You may consider fixing and resending the series as an independant series. Christophe
Powered by blists - more mailing lists