From: Marek Vasut <marex@denx.de>
To: "Nuno Sá" <noname.nuno@gmail.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Cc: linux-iio@vger.kernel.org, Daniel Baluta <daniel.baluta@nxp.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH] iio: core: WARN in case sample bits do not fit storage bits
Date: Tue, 22 Mar 2022 12:17:45 +0100 [thread overview]
Message-ID: <0dd8aca8-b2e7-5e62-d2bb-969dbc907593@denx.de> (raw)
In-Reply-To: <5be8958b14e252fcad9090ce911caa170e654186.camel@gmail.com>
On 3/22/22 11:10, Nuno Sá wrote:
Hi,
[...]
>>>> Arghh, completely forgot about this... Andy is right, maybe there
>>>> are
>>>> other cases (in which case, it would be nice to share :D), but
>>>> this one
>>>> is definitely one of them:
>>>>
>>>> https://elixir.bootlin.com/linux/latest/source/kernel/panic.c#L579
>>>>
>>>> You can have a cmdline parameter to panic on _WARN() and some
>>>> systems
>>>> may have it.
>>>
>>> Yes, I meant panic on warning.
>>>
>>> And I can't imagine that this driver can be system critical to the
>>> extent
>>> that we have to crash the system.
>>
>> Is there something which does trigger a backtrace, but without
>> panic()ing the system ?
>
> Nothing I'm aware... Other than directly call 'dump_stack()'
All right, dev_err() it is then. I sent V2.
prev parent reply other threads:[~2022-03-22 11:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 18:15 [PATCH] iio: core: WARN in case sample bits do not fit storage bits Marek Vasut
2022-03-21 9:08 ` Sa, Nuno
2022-03-21 10:40 ` Andy Shevchenko
2022-03-21 14:46 ` Marek Vasut
2022-03-21 16:10 ` Andy Shevchenko
2022-03-21 19:46 ` Marek Vasut
2022-03-22 7:43 ` Nuno Sá
2022-03-22 9:49 ` Andy Shevchenko
2022-03-22 9:57 ` Marek Vasut
2022-03-22 10:10 ` Nuno Sá
2022-03-22 11:17 ` Marek Vasut [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0dd8aca8-b2e7-5e62-d2bb-969dbc907593@denx.de \
--to=marex@denx.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel.baluta@nxp.com \
--cc=linux-iio@vger.kernel.org \
--cc=noname.nuno@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox