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:   Thu, 5 Apr 2018 04:23:57 -0700
From:   Matthew Wilcox <>
To:     Jia He <>
Cc:     Russell King <>,
        Catalin Marinas <>,
        Will Deacon <>,
        Mark Rutland <>,
        Ard Biesheuvel <>,
        Andrew Morton <>,
        Michal Hocko <>,
        Wei Yang <>,
        Kees Cook <>,
        Laura Abbott <>,
        Vladimir Murzin <>,
        Philip Derrin <>,
        AKASHI Takahiro <>,
        James Morse <>,
        Steve Capper <>,
        Pavel Tatashin <>,
        Gioh Kim <>,
        Vlastimil Babka <>, Mel Gorman <>,
        Johannes Weiner <>,
        Kemi Wang <>,
        Petr Tesarik <>,
        Andrey Ryabinin <>,
        Nikolay Borisov <>,
        Daniel Jordan <>,
        Daniel Vacek <>,
        Eugeniu Rosca <>,,,, Jia He <>
Subject: Re: [PATCH v7 1/5] mm: page_alloc: remain memblock_next_valid_pfn()
 on arm and arm64

On Thu, Apr 05, 2018 at 01:04:34AM -0700, Jia He wrote:
>  create mode 100644 include/linux/arm96_common.h

'arm96_common'?!  No.  Just no.

The right way to share common code is to create a header file (or use
an existing one), either in asm-generic or linux, with a #ifdef CONFIG_foo
block and then 'select foo' in the arm Kconfig files.  That allows this
common code to be shared, maybe with powerpc or x86 or ... in the future.

Powered by blists - more mailing lists