Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1737296
| From | Arvind Yadav <arvind.yadav.cs@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 0/4] iirqchip: Handle return value of kasprintf |
| Date | 2017-09-22 11:00 +0200 |
| Message-ID | <usrYv-3Z9-27@gated-at.bofh.it> (permalink) |
| References | <urIf0-kT-5@gated-at.bofh.it> <usrlM-3MM-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi Marc, On Friday 22 September 2017 01:40 PM, Marc Zyngier wrote: > On Wed, Sep 20 2017 at 1:38:18 pm BST, Arvind Yadav <arvind.yadav.cs@gmail.com> wrote: >> kasprintf() can fail here and we must check its return value. > Or not. The use of these strings is purely cosmetic (they are only used > to display various debug information), and printk is perfectly able to > handle a NULL string. > > Refusing to probe an essential piece of HW because a debug feature > failed seems at best counter-productive. Yes, Your are right. Sorry for noise. :) > Thanks, > > M. ~arvind
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH 0/4] iirqchip: Handle return value of kasprintf Arvind Yadav <arvind.yadav.cs@gmail.com> - 2017-09-20 10:10 +0200
[PATCH 3/4] irqchip/gic: Handle return value of kasprintf Arvind Yadav <arvind.yadav.cs@gmail.com> - 2017-09-20 10:10 +0200
[PATCH 1/4] irqchip/gic-v3-its: Handle return value of kasprintf Arvind Yadav <arvind.yadav.cs@gmail.com> - 2017-09-20 10:10 +0200
[PATCH 2/4] irqchip/gic-v3-its-platform-msi: Handle return value of kasprintf Arvind Yadav <arvind.yadav.cs@gmail.com> - 2017-09-20 10:10 +0200
Re: [PATCH 0/4] iirqchip: Handle return value of kasprintf Marc Zyngier <marc.zyngier@arm.com> - 2017-09-22 10:20 +0200
Re: [PATCH 0/4] iirqchip: Handle return value of kasprintf Arvind Yadav <arvind.yadav.cs@gmail.com> - 2017-09-22 11:00 +0200
csiph-web