linux-kernel - Re: [PATCH v4 0/4] MIPS: Modify mem= and memmap= parameter

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:   Sat, 5 Mar 2022 20:53:45 +0000 (GMT)
From:   "Maciej W. Rozycki" <macro@...am.me.uk>
To:     Mike Rapoport <rppt@...nel.org>
cc:     Tiezhu Yang <yangtiezhu@...ngson.cn>,
        Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Xuefeng Li <lixuefeng@...ngson.cn>, linux-mips@...r.kernel.org,
        linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 0/4] MIPS: Modify mem= and memmap= parameter

On Sat, 5 Mar 2022, Maciej W. Rozycki wrote:

>  Also to say (in said commit):
> 
> "There's no point to rewrite some logic to parse command line
> to pass initrd parameters or to declare a user memory area.
> We could use instead parse_early_param() that does the same
> thing."
> 
> is IMHO unfair given that the "rewrite" was there in place almost six 
> years before `parse_early_param' even started to exist!  Why do people 
> assume things have always been like they see them at the time they look?

 Self-correction for an incorrect last-moment edit: four years before 
rather than six (`parse_early_param' went in upstream shortly before:
<https://git.kernel.org/pub/scm/linux/kernel/git/ralf/linux.git/commit/?id=5145764263ab>).

  Maciej