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: <f613df39-6903-123b-a0f1-d1b783a755ce@huawei.com>
Date:   Tue, 8 Oct 2019 14:39:32 +0800
From:   Kefeng Wang <wangkefeng.wang@...wei.com>
To:     Petr Mladek <pmladek@...e.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>
CC:     Arnd Bergmann <arnd@...db.de>, Andy Whitcroft <apw@...onical.com>,
        "David S. Miller" <davem@...emloft.net>,
        Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
        Peter Zijlstra <peterz@...radead.org>,
        "Daniel Borkmann" <daniel@...earbox.net>,
        AlexeiStarovoitov <ast@...nel.org>,
        "Andrew Morton" <akpm@...ux-foundation.org>,
        GregKroah-Hartman <gregkh@...uxfoundation.org>,
        Joe Perches <joe@...ches.com>,
        "Arnaldo Carvalho de Melo" <acme@...hat.com>,
        Ingo Molnar <mingo@...hat.com>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/32] Kill pr_warning in the whole linux code

Hi all,

On 2019/10/2 16:55, Petr Mladek wrote:
> Linus,
> 
> On Fri 2019-09-20 14:25:12, Kefeng Wang wrote:
>> There are pr_warning and pr_warng to show WARNING level message,
>> most of the code using pr_warn, number based on next-20190919,
>>
>> pr_warn: 5189   pr_warning: 546 (tools: 398, others: 148)
> 
> The ratio is 10:1 in favor of pr_warn(). It would make sense
> to remove the pr_warning().
> 
> Would you accept pull request with these 32 simple patches
> for rc2, please?
> 
> Alternative is to run a simple sed. But it is not trivial
> to fix indentation of the related lines.

Kindly ping, should I respin patches with comments fixed?
Is the patchset acceptable, hope to be clear that what to do next :)

Thanks

> 
> Best Regards,
> Petr
> 
> .
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ