From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-sparse@vger.kernel.org
Cc: thomas.preston@codethink.co.uk, christopher.phang@codethink.co.uk
Subject: format updates for handing format attribute
Date: Thu, 1 Oct 2020 10:19:19 +0100 [thread overview]
Message-ID: <20201001091923.372349-1-ben.dooks@codethink.co.uk> (raw)
Hi, this is the update set for the format attributes.
I think the only thing I'm still thinking about is whether to
just merged patches 3 and 4.
branch:
https://gitlab.com/CodethinkLabs/sparse.git bjdooks/printf-v062
next reply other threads:[~2020-10-01 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 9:19 Ben Dooks [this message]
2020-10-01 9:19 ` [PATCH 1/4] tests: add varargs printf format tests Ben Dooks
2020-10-01 9:19 ` [PATCH 2/4] parse: initial parsing of __attribute__((format)) Ben Dooks
2020-10-01 9:19 ` [PATCH 3/4] add -Wformat Ben Dooks
2020-10-01 9:19 ` [PATCH 4/4] evaluate: check variadic argument types against formatting info Ben Dooks
2020-10-02 16:03 ` format updates for handing format attribute Luc Van Oostenryck
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=20201001091923.372349-1-ben.dooks@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=christopher.phang@codethink.co.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=thomas.preston@codethink.co.uk \
/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).