Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
To
: Alex Elder <elder@xxxxxxxxxx>
Subject
: Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
From
: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date
: Mon, 15 Apr 2024 01:07:41 -0700
Cc
: corbet@xxxxxxx, gregkh@xxxxxxxxxxxxxxxxxxx, workflows@xxxxxxxxxxxxxxx, linux-doc@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to
: <
20240414170850.148122-1-elder@linaro.org
>
References
: <
20240414170850.148122-1-elder@linaro.org
>
No, this advice is wronger than wrong. If you set panic_on_warn you get to keep the pieces.
Follow-Ups
:
Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
From:
Greg KH
References
:
[PATCH] Documentation: coding-style: don't encourage WARN*()
From:
Alex Elder
Prev by Date:
Re: [PATCH v2 1/2] KVM: x86: Add KVM_[GS]ET_CLOCK_GUEST for accurate KVM clock migration
Next by Date:
Re: (subset) [PATCH v2] drm: Document requirements for driver-specific KMS props in new drivers
Previous by thread:
Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
Next by thread:
Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
Index(es):
Date
Thread
[Index of Archives]
[Kernel Newbies]
[Security]
[Netfilter]
[Bugtraq]
[Linux FS]
[Yosemite Forum]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Samba]
[Video 4 Linux]
[Device Mapper]
[Linux Resources]
