linux-kernel - Re: linux-next: build failure after merge of the driver-core tree

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: <your-ad-here.call-01679929780-ext-1002@work.hours>
Date:   Mon, 27 Mar 2023 17:09:40 +0200
From:   Vasily Gorbik <gor@...ux.ibm.com>
To:     Greg KH <greg@...ah.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Heiko Carstens <hca@...ux.ibm.com>,
        Christian Borntraeger <borntraeger@...ibm.com>,
        Harald Freudenberger <freude@...ux.ibm.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the driver-core tree

On Mon, Mar 27, 2023 at 11:15:16AM +0200, Greg KH wrote:
> On Mon, Mar 27, 2023 at 07:22:15PM +1100, Stephen Rothwell wrote:
> > Hi All,
> > 
> > On Mon, 27 Mar 2023 09:33:42 +0200 Greg KH <greg@...ah.com> wrote:
> > >
> > > Patch is correct, thank you.
> > 
> > Thanks for checking.
> > 
> > > s390 developers, if you have a persistent tag/branch, I can suck this
> > > into the driver core tree and apply this fixup there so that you don't
> > > have to deal with any merge issues for 6.4-rc1 if you want.  Or I can
> > > provide one for you if you need/want that instead.  Or we can just leave
> > > it alone and deal with it during the 6.4-rc1 merge window, your choice.
> > 
> > Or (it being pretty trivial) you could both just let Linus know when
> > you send your merge requests ...
> 
> True, that works for me!

Sounds good for s390 as well, thank you!