linux-kernel - Re: [PATCH v2 1/4] mtd: spi-nor: cleanup common code

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: <20200914145022.rdjfaw5vzk7gzvfy@yadavpratyush.com>
Date:   Mon, 14 Sep 2020 20:20:22 +0530
From:   Pratyush Yadav <me@...avpratyush.com>
To:     Michael Walle <michael@...le.cc>
Cc:     linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Vignesh Raghavendra <vigneshr@...com>,
        Tudor Ambarus <tudor.ambarus@...rochip.com>,
        Richard Weinberger <richard@....at>,
        Miquel Raynal <miquel.raynal@...tlin.com>,
        Jungseung Lee <js07.lee@...sung.com>
Subject: Re: [PATCH v2 1/4] mtd: spi-nor: cleanup common code

On 14/09/20 01:09PM, Michael Walle wrote:
> Hi Pratyush,
> 
> Am 2020-09-14 11:40, schrieb Pratyush Yadav:
> > Hi Michael,
> > 
> > *sigh* This patch will cause a _lot_ of conflicts with my series [0]. It
> > should hopefully go in the next merge window so maybe you can rebase on
> > top of it? Dunno.
> 
> Could you pick up this patch in some form in your series? It looks like your
> series touches most/some of the functions. The patch just removes code
> repetitions.

I don't want to make any last-minute changes that could end up blocking 
the series. Its been pending for many months now.

> TBH I don't need this patch as I just can implement my new one-byte command
> using the current "if (nor->spimem) {} else {}" pattern.

It is up to you what you want to do about the patch. Maybe you can drop 
it now and send it later when things have settled down? Dunno.

-- 
Regards,
Pratyush Yadav