linux-kernel - Re: [PATCH] MIPS: lb60: Fix pin mappings

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: <20190611220441.2u4udxfmyjcdio65@pburton-laptop>
Date:   Tue, 11 Jun 2019 22:04:43 +0000
From:   Paul Burton <paul.burton@...s.com>
To:     Linus Walleij <linus.walleij@...aro.org>
CC:     Paul Cercueil <paul@...pouillou.net>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Ralf Baechle <ralf@...ux-mips.org>,
        James Hogan <jhogan@...nel.org>, "od@...c.me" <od@...c.me>,
        "linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        stable <stable@...r.kernel.org>
Subject: Re: [PATCH] MIPS: lb60: Fix pin mappings

Hi Linus / Paul,

On Sat, Jun 08, 2019 at 03:39:07PM +0200, Linus Walleij wrote:
> > Yes, that's definitely what's planned; right now the blockers are
> > patchsets [1] and [2]. [1] is ignored by everybody because there's no
> > maintainer for drivers/memory/. [2] is a year-long effort that still
> > doesn't show me the light at the end of the tunnel.
> >
> > [1] https://lkml.org/lkml/2019/6/4/743
> > [2] https://lkml.org/lkml/2019/5/21/679
> 
> What? That's unacceptable, the last resort is usually to send the
> patches to Andrew Morton (whether fair or not) when nothing gets
> applied.
> 
> In this case I would however encourage the MIPS maintainer to
> simply queue this stuff in the MIPS tree as blocking his arch work
> if not merged, Ralf would you consider just queueing this?
> I do not think the other Linus would mind.

I'd be happy to queue up [1] in mips-next, it looks pretty innocuous.

I can definitely feel Paul's pain on [2], but I see v12 is still getting
feedback so...

Thanks,
    Paul