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] [day] [month] [year] [list]
Message-ID: <20211024153300.GJ4721@alpha.franken.de>
Date:   Sun, 24 Oct 2021 17:33:00 +0200
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Ilya Lipnitskiy <ilya.lipnitskiy@...il.com>
Cc:     Jiri Kosina <trivial@...nel.org>,
        Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>,
        Serge Semin <Sergey.Semin@...kalelectronics.ru>,
        Hauke Mehrtens <hauke@...ke-m.de>, linux-mips@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/3] MIPS: kernel: proc: fix style and add CPU option
 reporting

On Wed, Oct 13, 2021 at 10:40:15PM -0700, Ilya Lipnitskiy wrote:
> Fix checkpatch errors and use seq_puts instead of seq_printf where
> possible.
> 
> Re-send an old patch that adds CPU option reporting.
> 
> Tested against MT7621 on OpenWrt running v5.10 kernel.
> 
> MT7621 output:
>   Options implemented   : tlb 4kex 4k_cache prefetch mcheck ejtag llsc
>   pindexed_dcache userlocal vint perf_cntr_intr_bit cdmm perf
> 
> ---
> v2: Add missing options that were added since the original patch
> v3: Resend after 6 months and add Hauke's Acked-by
> 
> Hauke Mehrtens (1):
>   MIPS: kernel: proc: add CPU option reporting
> 
> Ilya Lipnitskiy (2):
>   MIPS: kernel: proc: fix trivial style errors
>   MIPS: kernel: proc: use seq_puts instead of seq_printf
> 
>  arch/mips/kernel/proc.c | 227 ++++++++++++++++++++++++++++++++--------
>  1 file changed, 184 insertions(+), 43 deletions(-)

series applied to mips-next.

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