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] [day] [month] [year] [list]
Message-ID: <6d4240ab-b432-4753-bb6e-de0697f8db69@web.de>
Date: Fri, 4 Oct 2024 09:23:45 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Christophe Leroy <christophe.leroy@...roup.eu>,
 kernel-janitors@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
 Michael Ellerman <mpe@...erman.id.au>, Nathan Lynch <nathanl@...ux.ibm.com>,
 Nicholas Piggin <npiggin@...il.com>, Paul Moore <paul@...l-moore.com>
Cc: cocci@...ia.fr, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [v2 1/2] powerpc/pseries: Do not pass an error pointer to
 of_node_put() in pSeries_reconfig_add_node()

>> I was notified also about the following adjustment.
>>
>> …
>>   * linuxppc-dev: [resent,v2,1/2] powerpc/pseries: Do not pass an error pointer to of_node_put() in pSeries_reconfig_add_node()
>>       - https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpatchwork.ozlabs.org%2Fproject%2Flinuxppc-dev%2Fpatch%2Ff5ac19db-c7d5-9a94-aa37-9bb448fe665f%40web.de%2F&data=05%7C02%7Cchristophe.leroy%40csgroup.eu%7Cab19d1c85de343f5474908dce3cd8c02%7C8b87af7d86474dc78df45f69a2011bb5%7C0%7C0%7C638635719164841772%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=8b7APXbglDf13PvZ4nVh5Z92bEft2RBqU3LfKsUETOI%3D&reserved=0
>>       - for: Linux PPC development
>>      was: New
>>      now: Changes Requested
>> …
>>
>> It seems that I can not see so far why this status update happened
>> for any reasons.
>> Will further clarifications become helpful here?
>
> Sorry I forgot to send the email. It is the same kind of problem as the other series: Message IDs and/or In-Reply-To headers are messed up

Three mailing list archive interfaces can present a mostly consistent view for
the involved message threads, can't they?


> and b4 ends up applying an unrelated patch instead of applying the series as you can see below:
>
> $ b4 shazam f5ac19db-c7d5-9a94-aa37-9bb448fe665f@....de
…

This development tool is also still evolving.
Are you looking for corresponding software extensions?
https://b4.docs.kernel.org/en/latest/#getting-help

How do you think about to start with the desired cover letter from the provided patch series
for another integration attempt?

Regards,
Markus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ