All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>,
	"Luc Van Oostenryck" <luc.vanoostenryck@gmail.com>,
	linux-sparse@vger.kernel.org
Cc: Jeff Layton <jlayton@redhat.com>
Subject: Re: [ANNOUNCE] Sparse v0.6.4
Date: Tue, 28 Sep 2021 23:43:36 +0100	[thread overview]
Message-ID: <73f07821-4abe-2194-96a2-296c54c47074@ramsayjones.plus.com> (raw)
In-Reply-To: <5bfca92e-1eb0-ab7d-80b5-5ea2134ae928@kleine-koenig.org>



On 28/09/2021 20:56, Uwe Kleine-König wrote:
> Hi Luc,
> 
> On 9/6/21 6:21 AM, Luc Van Oostenryck wrote:
>> Sparse v0.6.4 is now out.
> 
> I finally came around to update the Debian packaging. There is just a (non-critical) problem on x32 where some tests fail. I didn't look deeply, but if you care, now you know :-)
> 
> https://buildd.debian.org/status/fetch.php?pkg=sparse&arch=x32&ver=0.6.4-1&stamp=1632795062&raw=0


Hmm, interesting. I tested on Linux Mint 19 32-bit and didn't see any
failures. As far as I can tell, only the 'validation/builtin-objsize0.c'
test is failing (squinting hard at the above!).

Unfortunately, I can't test again tonight, but I will try and take a look
at it tomorrow.

ATB,
Ramsay Jones


  reply	other threads:[~2021-09-28 22:43 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
2021-09-28 21:05     ` Ben Dooks
2021-09-28 19:56 ` Uwe Kleine-König
2021-09-28 22:43   ` Ramsay Jones [this message]
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=73f07821-4abe-2194-96a2-296c54c47074@ramsayjones.plus.com \
    --to=ramsay@ramsayjones.plus.com \
    --cc=jlayton@redhat.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.