From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Add printf/scanf -Wformat checking
Date: Fri, 17 Oct 2025 08:47:29 +0100 [thread overview]
Message-ID: <d9765def-8b4f-4892-bb8f-13a0a7eb01ca@codethink.co.uk> (raw)
In-Reply-To: <CAADWXX_kGbSjXrt9ZQGLg7R_ioEnqvZ_s+asrPAPgNnQ_LbaBQ@mail.gmail.com>
On 16/10/2025 18:12, Linus Torvalds wrote:
> On Thu, Oct 16, 2025 at 4:04 AM Ben Dooks <ben.dooks@codethink.co.uk> wrote:
>>
>> [re-send as I can't type sparse and messages didn't get to the list]
>
> You may need to re-send again after fixing your mailer setup, because
> while it made it to the list, I suspect a lot of people didn't
> actually get it, because it fails DKIM checks and that then tends to
> mean that it gets marked as spam.
>
> At least it did for me - but I check my spam folder daily, so I noticed.
>
> The reason it fails DKIM is that your codethink DKIM setup is scrogged.
Thanks, passed this on to our IT support.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
https://www.codethink.co.uk/privacy.html
next prev parent reply other threads:[~2025-10-17 7:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 11:04 Add printf/scanf -Wformat checking Ben Dooks
2025-10-16 11:04 ` [PATCH RESEND 1/4] parse: initial parsing of __attribute__((format)) Ben Dooks
2025-10-16 11:04 ` [PATCH RESEND 2/4] add -Wformat Ben Dooks
2025-10-16 11:04 ` [PATCH RESEND 3/4] evaluate: check variadic argument types against formatting info Ben Dooks
2025-10-16 11:04 ` [PATCH RESEND 4/4] tests: add varargs printf format tests Ben Dooks
2025-10-16 17:12 ` Add printf/scanf -Wformat checking Linus Torvalds
2025-10-17 7:47 ` Ben Dooks [this message]
2025-10-20 10:01 ` Ben Dooks
-- strict thread matches above, loose matches on Subject: below --
2025-10-20 15:39 Ben Dooks
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=d9765def-8b4f-4892-bb8f-13a0a7eb01ca@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=torvalds@linux-foundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).