From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: submit-checklist: structure by category
Date: Tue, 27 Feb 2024 09:57:35 +0100 [thread overview]
Message-ID: <CAMuHMdUD94XuE_7UK3TEWbeZ2eMOPimDi-xoo9+43FhY3O2aDA@mail.gmail.com> (raw)
In-Reply-To: <43df625f-bd32-4dd9-a960-6d0f5c0304c7@infradead.org>
Hi Randy,
On Tue, Feb 27, 2024 at 1:41 AM Randy Dunlap <rdunlap@infradead.org> wrote:
> > - Concerning checking with tools, checkpatch probably still makes sense;
> > it pointed out in several places. If sparse and checkstack are really
> > the next two tools to point out, I am not so sure about.
>
> I doubt that ckeckstack is important since gcc & clang warn us about
> stack usage.
True, but that would leave you without a tool to get figures when
there is no excess stack usage detected by the compiler.
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
next prev parent reply other threads:[~2024-02-27 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 10:46 [PATCH] docs: submit-checklist: structure by category Lukas Bulwahn
2024-02-26 12:48 ` Jani Nikula
2024-02-27 7:28 ` Lukas Bulwahn
2024-02-27 0:41 ` Randy Dunlap
2024-02-27 8:04 ` Lukas Bulwahn
2024-02-27 8:57 ` Geert Uytterhoeven [this message]
2024-02-27 11:03 ` Lukas Bulwahn
2024-02-27 11:24 ` Geert Uytterhoeven
2024-02-28 21:57 ` Jonathan Corbet
2024-02-28 23:03 ` Randy Dunlap
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=CAMuHMdUD94XuE_7UK3TEWbeZ2eMOPimDi-xoo9+43FhY3O2aDA@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=corbet@lwn.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=rdunlap@infradead.org \
--cc=workflows@vger.kernel.org \
/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).