From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: Re: [PATCH v3 0/5] fix list corruption with recursive remove_usage()
Date: Sat, 5 Aug 2017 00:32:03 +0200 [thread overview]
Message-ID: <CAExDi1Ra9v5QXoP-oSRH6J7XFadMAO5BC79e0e9+-FMjvnwmNw@mail.gmail.com> (raw)
In-Reply-To: <20170804215321.66392-1-luc.vanoostenryck@gmail.com>
Please ignore this one. I just resent a -v4.
-- Luc
next prev parent reply other threads:[~2017-08-04 22:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 21:53 [PATCH v3 0/5] fix list corruption with recursive remove_usage() Luc Van Oostenryck
2017-08-04 21:53 ` [PATCH v3 1/5] ptrlist: add a counter for the number of removed elemnets Luc Van Oostenryck
2017-08-04 21:53 ` [PATCH v3 2/5] ptrlist: adjust ptr_list_size for the new ->rm field Luc Van Oostenryck
2017-08-04 21:53 ` [PATCH v3 3/5] ptrlist: add MARK_CURRENT_DELETED Luc Van Oostenryck
2017-08-04 21:53 ` [PATCH v3 4/5] ptrlist: avoid iteration on NULL entries Luc Van Oostenryck
2017-08-04 21:53 ` [PATCH v3 5/5] mark pseudo users as deleted instead of removing them Luc Van Oostenryck
2017-08-04 22:32 ` Luc Van Oostenryck [this message]
2017-08-05 0:24 ` [PATCH v3 0/5] fix list corruption with recursive remove_usage() Christopher Li
2017-08-05 8:55 ` Luc Van Oostenryck
2017-08-05 11:28 ` Christopher Li
2017-08-05 23:04 ` Luc Van Oostenryck
2017-08-06 0:09 ` Christopher Li
2017-08-06 1:07 ` Luc Van Oostenryck
2017-08-05 11:45 ` Christopher Li
-- strict thread matches above, loose matches on Subject: below --
2017-08-04 22:17 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=CAExDi1Ra9v5QXoP-oSRH6J7XFadMAO5BC79e0e9+-FMjvnwmNw@mail.gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--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 NNTP newsgroup(s).