linux-kernel - Re: [PATCH 0/4] part2: kill pr

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: <e32f48b2-2286-912f-b8e2-1b1bcd892e07@huawei.com>
Date:   Fri, 29 Nov 2019 20:56:01 +0800
From:   Kefeng Wang <wangkefeng.wang@...wei.com>
To:     Petr Mladek <pmladek@...e.com>
CC:     <joe@...ches.com>, <linux-kernel@...r.kernel.org>,
        <gregkh@...uxfoundation.org>, <tj@...nel.org>, <arnd@...db.de>,
        <sergey.senozhatsky@...il.com>, <rostedt@...dmis.org>
Subject: Re: [PATCH 0/4] part2: kill pr_warning from kernel



On 2019/11/29 19:58, Petr Mladek wrote:
> On Thu 2019-11-28 08:47:48, Kefeng Wang wrote:
>> This is the part2 of kill pr_warning, as most pr_warning conversion merged
>> into v5.5, let's cleanup the last two stragglers. Then, completely drop
>> pr_warning defination in printk.h and check in checkpatch.pl.
>>
>> Part1: https://lore.kernel.org/lkml/20190920062544.180997-1-wangkefeng.wang@huawei.com
>>
>> Kefeng Wang (4):
>>   workqueue: Use pr_warn instead of pr_warning
>>   staging: isdn: gigaset: Use pr_warn instead of pr_warning
> 
> This one is already in mainline via staging tree.
> 
>>   printk: Drop pr_warning definition
>>   checkpatch: Drop pr_warning check
> 
> The other patches are committed in printk.git, branch
> for-5.5-pr-warning-removal.
> 
> I am going to sent pull request after 5.5-rc1 is tagged.
> It is should be fine according to linux-next. But I am not
> sure if all coming changes are really tested in linux-next.
> 
Hi Petr, thanks, the issue will always be there, so let's remove
the definition ASAP, and we can fix the follow-up possible use :)


> Best Regards,
> Petr
> 
> .
>