From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Dan Carpenter <error27@gmail.com>
Cc: Li Yang <lidaxian@hust.edu.cn>,
Magnus Damm <magnus.damm@gmail.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: renesas: renesas-soc: release 'chipid' from ioremap()
Date: Mon, 3 Apr 2023 09:46:09 +0200 [thread overview]
Message-ID: <CAMuHMdVE3Fcb9Rx9bF4NTyGH=gdRY3maNY6S5W7iFFiGrFeOJw@mail.gmail.com> (raw)
In-Reply-To: <302d88ca-7d28-4450-8e60-d0bb40f4174d@kili.mountain>
Hi Dan,
On Mon, Apr 3, 2023 at 9:34 AM Dan Carpenter <error27@gmail.com> wrote:
> On Mon, Apr 03, 2023 at 09:12:55AM +0200, Geert Uytterhoeven wrote:
> > Perhaps we need a different mechanism to annotate error handling code
> > that cannot ever happen in a real product, so it can be thrown away by
> > the compiler, while still pleasing the static checkers? All these
> > checks and error handling code do affect kernel size. There are
> > Linux products running on SoCs with 8 MiB of internal SRAM.
>
> People sometimes call BUG_ON(!soc_dev_attr). It's sort of rare these
BUG_ON() is also not cheap, space-wise (except if CONFIG_BUG=n).
> days. It would be easy to make a function which silences Smatch...
>
> __system_is_dead();
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2023-04-03 7:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 9:55 [PATCH] soc: renesas: renesas-soc: release 'chipid' from ioremap() Li Yang
2023-03-31 12:13 ` Geert Uytterhoeven
2023-04-01 8:22 ` Dan Carpenter
2023-04-03 7:12 ` Geert Uytterhoeven
2023-04-03 7:34 ` Dan Carpenter
2023-04-03 7:46 ` Geert Uytterhoeven [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='CAMuHMdVE3Fcb9Rx9bF4NTyGH=gdRY3maNY6S5W7iFFiGrFeOJw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=error27@gmail.com \
--cc=lidaxian@hust.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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;
as well as URLs for NNTP newsgroup(s).