[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166488986181.779920.10714540040506715558.b4-ty@ellerman.id.au>
Date: Wed, 05 Oct 2022 00:24:21 +1100
From: Michael Ellerman <patch-notifications@...erman.id.au>
To: David Hildenbrand <david@...hat.com>, linux-kernel@...r.kernel.org
Cc: Jonathan Corbet <corbet@....net>, Baoquan He <bhe@...hat.com>,
Andy Whitcroft <apw@...onical.com>,
Dwaipayan Ray <dwaipayanray1@...il.com>,
Lukas Bulwahn <lukas.bulwahn@...il.com>,
Ingo Molnar <mingo@...nel.org>, linuxppc-dev@...ts.ozlabs.org,
linux-doc@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Michael Ellerman <mpe@...erman.id.au>,
Jani Nikula <jani.nikula@...ux.intel.com>,
Vivek Goyal <vgoyal@...hat.com>,
Dave Young <dyoung@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Joe Perches <joe@...ches.com>,
Nicholas Piggin <npiggin@...il.com>,
David Laight <David.Laight@...LAB.COM>, linux-mm@...ck.org,
Christophe Leroy <christophe.leroy@...roup.eu>
Subject: Re: (subset) [PATCH v1 0/3] coding-style.rst: document BUG() and WARN() rules
On Tue, 20 Sep 2022 14:22:59 +0200, David Hildenbrand wrote:
> As it seems to be rather unclear if/when to use BUG(), BUG_ON(),
> VM_BUG_ON(), WARN_ON_ONCE(), ... let's try to document the result of a
> recent discussion.
>
> Details can be found in patch #1.
>
> RFC -> v1:
> * "coding-style.rst: document BUG() and WARN() rules ("do not crash the
> kernel")"
> -> Rephrase/extend according to John
> -> Add some details regarding the use of panic()
> * powerpc/prom_init: drop PROM_BUG()
> -> Added
> * "checkpatch: warn on usage of VM_BUG_ON() and other BUG variants"
> -> Warn on more variants
>
> [...]
Patch 2 applied to powerpc/next.
[2/3] powerpc/prom_init: drop PROM_BUG()
https://git.kernel.org/powerpc/c/c4167aec98524fa4511b3222303a758b532b6009
cheers
Powered by blists - more mailing lists