From: Wolfgang Denk <wd@denx.de>
To: Tom Rini <trini@konsulko.com>
Cc: Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
Stefan Roese <sr@denx.de>,
u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH v4 07/10] watchdog: wdt-uclass.c: handle all DM watchdogs in watchdog_reset()
Date: Fri, 13 Aug 2021 08:17:24 +0200 [thread overview]
Message-ID: <631933.1628835444@gemini.denx.de> (raw)
In-Reply-To: <20210812162034.GY858@bill-the-cat>
Dear Tom,
In message <20210812162034.GY858@bill-the-cat> you wrote:
>
> > So if "the system is on fire" is one of the cases where an error
> > message should be omitted to save maybe 50 or 100 bytes of image
> > size? This sounds wrong to me.
>
> It sounds right to me because it's unlikely everything caught fire
> because of this call right here and likely it's because of one of the
> messages much further up on the console log. Hopefully we haven't
> caused that message to be unavailable now due to unhelpful failure
> messages.
Omitting code to handle situations that are unlikely to happen is
definitely not what I consider robust programming, and nothing which
I would let pass a code review.
But if you insist, there is no more to do for me here that to note
that fact that we disagree.
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
People are very flexible and learn to adjust to strange surroundings
-- they can become accustomed to read Lisp and Fortran programs, for
example. - Leon Sterling and Ehud Shapiro, Art of Prolog, MIT Press
next prev parent reply other threads:[~2021-08-13 6:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 15:00 [PATCH v4 00/10] handling all DM watchdogs in watchdog_reset() Rasmus Villemoes
2021-08-02 15:00 ` [PATCH v4 01/10] watchdog: wdt-uclass.c: use wdt_start() in wdt_expire_now() Rasmus Villemoes
2021-08-02 15:00 ` [PATCH v4 02/10] watchdog: wdt-uclass.c: introduce struct wdt_priv Rasmus Villemoes
2021-08-03 6:30 ` Stefan Roese
2021-08-02 15:00 ` [PATCH v4 03/10] watchdog: wdt-uclass.c: neaten UCLASS_DRIVER definition Rasmus Villemoes
2021-08-02 15:00 ` [PATCH v4 04/10] watchdog: wdt-uclass.c: refactor initr_watchdog() Rasmus Villemoes
2021-08-02 15:00 ` [PATCH v4 05/10] watchdog: wdt-uclass.c: keep track of each device's running state Rasmus Villemoes
2021-08-02 15:00 ` [PATCH v4 06/10] sandbox: disable CONFIG_WATCHDOG_AUTOSTART Rasmus Villemoes
2021-08-02 15:00 ` [PATCH v4 07/10] watchdog: wdt-uclass.c: handle all DM watchdogs in watchdog_reset() Rasmus Villemoes
2021-08-02 19:22 ` Simon Glass
2021-08-03 6:29 ` Stefan Roese
2021-08-03 8:28 ` Stefan Roese
2021-08-11 11:32 ` Rasmus Villemoes
2021-08-11 11:49 ` Stefan Roese
2021-08-11 12:13 ` Rasmus Villemoes
2021-08-11 12:19 ` Stefan Roese
2021-08-11 12:29 ` Wolfgang Denk
2021-08-11 12:43 ` Tom Rini
2021-08-12 6:40 ` Wolfgang Denk
2021-08-12 13:48 ` Tom Rini
2021-08-12 14:12 ` Simon Glass
2021-08-12 14:21 ` Wolfgang Denk
2021-08-12 16:20 ` Tom Rini
2021-08-13 6:17 ` Wolfgang Denk [this message]
2021-08-17 9:28 ` Stefan Roese
2021-08-17 12:35 ` Tom Rini
2021-08-27 6:30 ` Stefan Roese
2021-08-27 12:26 ` Tom Rini
2021-08-02 15:00 ` [PATCH v4 08/10] watchdog: add gpio watchdog driver Rasmus Villemoes
2021-08-02 15:00 ` [PATCH v4 09/10] sandbox: add test of wdt_gpio driver Rasmus Villemoes
2021-08-02 15:00 ` [PATCH v4 10/10] sandbox: add test of wdt-uclass' watchdog_reset() Rasmus Villemoes
2021-08-11 6:05 ` [PATCH v4 00/10] handling all DM watchdogs in watchdog_reset() Rasmus Villemoes
2021-08-11 6:10 ` Stefan Roese
2021-08-11 6:19 ` Rasmus Villemoes
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=631933.1628835444@gemini.denx.de \
--to=wd@denx.de \
--cc=rasmus.villemoes@prevas.dk \
--cc=sjg@chromium.org \
--cc=sr@denx.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.