From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Chris Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: Re: [PATCH RESEND2 1/4] parse: initial parsing of __attribute__((format))
Date: Mon, 22 Dec 2025 11:49:08 +0000 [thread overview]
Message-ID: <11df30dc-e1d9-4f40-a9ac-43cb1af69da0@codethink.co.uk> (raw)
In-Reply-To: <CACePvbVvsAPURh+jfb2Vh8cPsOzuR2HmzuD9j5Gf6GJyD2orng@mail.gmail.com>
On 01/12/2025 19:23, Chris Li wrote:
> Hi Ben,
>
> Thanks for the patch and sorry for the late reply.
>
> Your format attribute series work applies to the sparse-dev tree fine
> and "make check" runs fine as well. Thank you so much.
>
> I have some trivial coding style of feedback for you, see the comments
> below. Mostly just nitpicks, does not impact the coding behavior. Let
> me know if you want to update a new series or I can be lazy and just
> apply your current series.
Thank you. I've implemented most of your parse.c/symbol.h changes now.
I am not actually back at work until 2nd-Jan 2026 so may not get
all the other changes sorted.
--
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-12-22 12:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 15:39 Add printf/scanf -Wformat checking Ben Dooks
2025-10-20 15:39 ` [PATCH RESEND2 1/4] parse: initial parsing of __attribute__((format)) Ben Dooks
2025-12-01 19:23 ` Chris Li
2025-12-22 11:49 ` Ben Dooks [this message]
2026-01-17 0:14 ` Chris Li
2025-10-20 15:39 ` [PATCH RESEND2 2/4] add -Wformat Ben Dooks
2025-10-20 15:39 ` [PATCH RESEND2 3/4] evaluate: check variadic argument types against formatting info Ben Dooks
2025-12-01 19:52 ` Chris Li
2025-10-20 15:39 ` [PATCH RESEND2 4/4] tests: add varargs printf format tests 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=11df30dc-e1d9-4f40-a9ac-43cb1af69da0@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=sparse@chrisli.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).