From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: "Uwe Kleine-König / sparse"
<gitlab+7f2b156a8ad4ece3334e6b9712c2de05@salsa.debian.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: sparse | upgrade to upstream v0.6.2 (!2)
Date: Sat, 1 Aug 2020 18:54:24 +0200 [thread overview]
Message-ID: <20200801165424.e5uxzbpwrkt3suo6@ltop.local> (raw)
In-Reply-To: <note_184887@salsa.debian.org>
On Sat, Aug 01, 2020 at 06:51:42AM +0000, Uwe Kleine-König wrote:
> Uwe Kleine-König commented:
>
>
> What I didn't do compared to your MR is to add the patch "gensel: remove unneeded test/uninitialized warning" to fix a build warning.
I've added a 'maintenance' branch on the official tree:
git://git.kernel.org/pub/scm/devel/sparse/sparse.git maint-v0.6.2
which contains a few fixup patches I think the Debian release should have.
It contains, the 'gensel' patch here above (not very important, it just fix
a warning), your patch for sindex.1 (same), the build fix for Hurd and
most importantly it contains a patch for a real bug making sparse crash:
77f35b796cc8 ("generic: fix missing inlining of generic expression")
Thanks,
-- Luc
next parent reply other threads:[~2020-08-01 16:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <reply-7f2b156a8ad4ece3334e6b9712c2de05@salsa.debian.org>
[not found] ` <merge_request_28506@salsa.debian.org>
[not found] ` <note_184887@salsa.debian.org>
2020-08-01 16:54 ` Luc Van Oostenryck [this message]
[not found] ` <note_184882@salsa.debian.org>
2020-08-02 13:29 ` sparse | upgrade to upstream v0.6.2 (!2) Luc Van Oostenryck
2020-08-09 19:21 ` Luc Van Oostenryck
[not found] ` <note_185118@salsa.debian.org>
[not found] ` <note_185156@salsa.debian.org>
2020-08-02 21:09 ` Luc Van Oostenryck
[not found] ` <note_185002@salsa.debian.org>
[not found] ` <note_185155@salsa.debian.org>
2020-08-02 21:30 ` Luc Van Oostenryck
2020-08-03 14:53 ` Alexey Gladkov
2020-08-04 16:38 ` Alexey Gladkov
2020-08-04 18:52 ` Oleg Nesterov
2020-08-04 19:33 ` Luc Van Oostenryck
2020-08-04 20:02 ` Luc Van Oostenryck
2020-08-05 10:16 ` Alexey Gladkov
[not found] <note_185299@salsa.debian.org>
[not found] ` <note_185431@salsa.debian.org>
[not found] ` <note_185453@salsa.debian.org>
[not found] ` <note_185458@salsa.debian.org>
[not found] ` <note_185460@salsa.debian.org>
[not found] ` <note_185461@salsa.debian.org>
[not found] ` <note_185530@salsa.debian.org>
[not found] ` <note_185532@salsa.debian.org>
[not found] ` <20200805110418.iutr56vyewhbqr7v@ltop.local>
[not found] ` <20200805112141.ier2xkhm5sqjtbck@comp-core-i7-2640m-0182e6>
2020-08-05 15:20 ` Luc Van Oostenryck
2020-08-05 15:44 ` Alexey Gladkov
2020-08-05 19:58 ` 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=20200801165424.e5uxzbpwrkt3suo6@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=gitlab+7f2b156a8ad4ece3334e6b9712c2de05@salsa.debian.org \
--cc=linux-sparse@vger.kernel.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).