linux-kernel - Re: linux-next: build failure after merge of the akpm 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] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 21 Feb 2020 10:59:40 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Arjun Roy <arjunroy@...gle.com>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        David Miller <davem@...emloft.net>
Subject: Re: linux-next: build failure after merge of the akpm tree

Hi Arjun,

On Thu, 20 Feb 2020 15:44:28 -0800 Arjun Roy <arjunroy@...gle.com> wrote:
>
> On Thu, Feb 20, 2020 at 3:43 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > On Thu, 20 Feb 2020 15:22:04 -0800 Arjun Roy <arjunroy@...gle.com> wrote:  
> > >
> > > I have a possible solution in mind, but it would involve a slight
> > > change in the SPARC macro (to be more inline with the semantics of the
> > > other platforms).
> > > If you're open to such a change, I can send it out.  
> >
> > Its not up to me :-)
> >
> > If it is not too much work, I would say, do the patch, test it as you
> > can, then send it out cc'ing the Sparc maintainer (DaveM cc'd) and see
> > what happens.
> 
> Certainly, I will do so.

Just one thing: its worth while making it clear to DaveM that you just
want his Ack (rather than for him to take the patch into the Sparc
tree) so that the patch can go into Andrew's tree along with the rest
of the series.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped