From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-sparse@vger.kernel.org, "Jeff Layton" <jlayton@redhat.com>,
"Uwe Kleine-König" <uwe@kleine-koenig.org>
Subject: Re: [ANNOUNCE] Sparse v0.6.4
Date: Tue, 7 Sep 2021 08:29:28 +0200 [thread overview]
Message-ID: <20210907062928.qy37irlznwborcab@mail> (raw)
In-Reply-To: <0c4480ce-6c92-7788-772c-581a76c2df51@codethink.co.uk>
On Mon, Sep 06, 2021 at 11:04:14AM +0100, Ben Dooks wrote:
> On 06/09/2021 05:21, Luc Van Oostenryck wrote:
> > Sparse v0.6.4 is now out.
> >
> > The source code can be found at its usual repository:
> > git://git.kernel.org/pub/scm/devel/sparse/sparse.git v0.6.4
> >
> > The tarballs can be found at:
> > https://www.kernel.org/pub/software/devel/sparse/dist/
> >
> > Many thanks to people who have somehow contributed to the 299
> > patches of this release:
> > Ramsay Jones, Linus Torvalds, Kyle Russell
>
> This has reminded me I have lost track of the printf formatting
> changes. Is it possible to re-sync and work out what still needs
> to be done to get this work merged?
Sure, the series can be merged with just a few trival conflicts.
I think things were left at
https://lore.kernel.org/linux-sparse/20201013232231.10349-1-luc.vanoostenryck@gmail.com/T/#ma187dd3978640fccac03c0194fd5bdd84c437721
but the series is now at:
git://github.com/lucvoo/sparse-dev.git format-check
Are these patches fine for you?
-- Luc
next prev parent reply other threads:[~2021-09-07 6:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 4:21 [ANNOUNCE] Sparse v0.6.4 Luc Van Oostenryck
2021-09-06 10:04 ` Ben Dooks
2021-09-07 6:29 ` Luc Van Oostenryck [this message]
2021-09-28 21:05 ` Ben Dooks
2021-09-28 19:56 ` Uwe Kleine-König
2021-09-28 22:43 ` Ramsay Jones
2021-09-29 6:54 ` Uwe Kleine-König
2021-09-29 21:35 ` Ramsay Jones
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=20210907062928.qy37irlznwborcab@mail \
--to=luc.vanoostenryck@gmail.com \
--cc=ben.dooks@codethink.co.uk \
--cc=jlayton@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=uwe@kleine-koenig.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).