linux-kernel - Re: [PATCH 05/12] firmware: dmi-id: add a release callback function

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: <20240413223857.7c01985f@endymion.delvare>
Date: Sat, 13 Apr 2024 22:38:57 +0200
From: Jean Delvare <jdelvare@...e.de>
To: "Arnd Bergmann" <arnd@...db.de>, "Stephen Rothwell"
 <sfr@...b.auug.org.au>
Cc: "Arnd Bergmann" <arnd@...nel.org>, linux-kbuild@...r.kernel.org,
 "Masahiro Yamada" <masahiroy@...nel.org>, "Nathan Chancellor"
 <nathan@...nel.org>, "Greg Kroah-Hartman" <gregkh@...e.de>, "Nicolas
 Schier" <nicolas@...sle.eu>, "Nick Desaulniers" <ndesaulniers@...gle.com>,
 "Bill Wendling" <morbo@...gle.com>, "Justin Stitt"
 <justinstitt@...gle.com>, linux-kernel@...r.kernel.org,
 llvm@...ts.linux.dev, "Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: [PATCH 05/12] firmware: dmi-id: add a release callback function

On Fri, 12 Apr 2024 11:42:03 +0200, Arnd Bergmann wrote:
> On Mon, Apr 8, 2024, at 09:59, Jean Delvare wrote:
> > On Thu, 04 Apr 2024 16:07:55 +0200, Arnd Bergmann wrote:  
> >> On Fri, Mar 29, 2024, at 13:49, Jean Delvare wrote:  
> >> > Will you get this upstream, or do you expect me to take it in my
> >> > dmi/for-next branch?    
> >> 
> >> It would help me if you can apply it to your tree directly.  
> >
> > OK, it's in my dmi-for-next branch now:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging.git/log/?h=dmi-for-next  
> 
> I see it's in your tree, but I don't see your tree in linux-next.
>
> As all the other fixes from my series got merged, I would like to
> merge the patches that turn the warnings on, but that still
> causes a build-time regression.
> 
> Is there a reason for the dmi-next tree not being part of
> linux-next, or should we ask Stephen (added to Cc) to add it?

Hmm, Stephen cleaned up the list of trees he pulls from 2 months ago.
Back then, I objected that I may use my tree again in the future, and I
thought he had added it back to the list, but maybe I misunderstood.

Stephen, can you check if you still pull from tree above, and if not,
add it back to the list? Thanks in advance.

-- 
Jean Delvare
SUSE L3 Support