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: <20200728123323.GA14660@alpha.franken.de>
Date:   Tue, 28 Jul 2020 14:33:23 +0200
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Krzysztof Kozlowski <krzk@...nel.org>
Cc:     Paul Cercueil <paul@...pouillou.net>,
        "H. Nikolaus Schaller" <hns@...delico.com>,
        linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
        Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v4 2/2] MIPS: ingenic: Enable JZ4780_NEMC manually

On Tue, Jul 28, 2020 at 02:00:35PM +0200, Krzysztof Kozlowski wrote:
> On Tue, Jul 28, 2020 at 01:37:02PM +0200, Thomas Bogendoerfer wrote:
> > On Tue, Jul 28, 2020 at 01:19:35PM +0200, Krzysztof Kozlowski wrote:
> > > On Tue, Jul 28, 2020 at 01:12:11PM +0200, Paul Cercueil wrote:
> > > > Hi Krzysztof,
> > > > 
> > > > Le mar. 28 juil. 2020 à 12:45, Krzysztof Kozlowski <krzk@...nel.org> a écrit
> > > > :
> > > > > The CONFIG_JZ4780_NEMC was previously a default on MIPS but now it has
> > > > > to be enabled manually.
> > > > > 
> > > > > Signed-off-by: Krzysztof Kozlowski <krzk@...nel.org>
> > > > 
> > > > I think you should swap the two so that there are no problems when
> > > > bisecting.
> > > 
> > > Good point. I was thinking that it will go via some of MIPS trees and
> > > the patch #1 will just wait a cycle.  However with acks, I can take it
> > > through drivers/memory tree.
> > 
> > I've acked the patch.
> > 
> > Thomas.
> 
> Thanks but now I noticed that one of changed configs
> (arch/mips/configs/rs90_defconfig) is only in MIPS tree.
> 
> I think it is easier then to take the patch #2 (configs) via MIPS and
> wait with #1 for the next cycle or also take it via MIPS if it applies
> cleanly.

ok, I'll take it.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ