Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1738857
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] firmware: dmi_scan: Drop dmi_initialized |
| Date | 2017-09-25 11:30 +0200 |
| Message-ID | <utxSa-4rR-9@gated-at.bofh.it> (permalink) |
| References | <uqZhT-3xJ-1@gated-at.bofh.it> <usQkb-22V-41@gated-at.bofh.it> <usUxr-4MR-11@gated-at.bofh.it> <utbeW-6SD-5@gated-at.bofh.it> <utxyN-4k5-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Sep 25, 2017 at 11:00:11AM +0200, Jean Delvare wrote: > Then we have that in common. While reading the code and its history, I > was worried that the justification to add this warning in the first > place was technically weak. Not every coding error must automatically > translate to a patch to make the code robust against said error. > Sometimes you just have to admit that you did not pay attention as you > should have, fix your mistake, possibly document it for others, and > move on. Otherwise we end up with slow bloated code. That WARN_ON() is a form of documentation. And if you care about performance for your code path, hide it under some CONFIG_*_DEBUG, but in general WARN_ON() isn't terribly expensive (depending entirely on the complexity of the condition of course).
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] firmware: dmi_scan: Drop dmi_initialized Jean Delvare <jdelvare@suse.de> - 2017-09-18 10:10 +0200
Re: [PATCH] firmware: dmi_scan: Drop dmi_initialized Ingo Molnar <mingo@kernel.org> - 2017-09-23 13:00 +0200
Re: [PATCH] firmware: dmi_scan: Drop dmi_initialized Jean Delvare <jdelvare@suse.de> - 2017-09-23 17:30 +0200
Re: [PATCH] firmware: dmi_scan: Drop dmi_initialized Ingo Molnar <mingo@kernel.org> - 2017-09-24 11:20 +0200
Re: [PATCH] firmware: dmi_scan: Drop dmi_initialized Jean Delvare <jdelvare@suse.de> - 2017-09-25 11:10 +0200
Re: [PATCH] firmware: dmi_scan: Drop dmi_initialized Peter Zijlstra <peterz@infradead.org> - 2017-09-25 11:30 +0200
Re: [PATCH] firmware: dmi_scan: Drop dmi_initialized Peter Zijlstra <peterz@infradead.org> - 2017-09-25 11:30 +0200
csiph-web