From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] fix list corruption with recursive remove_usage()
Date: Sun, 6 Aug 2017 03:07:58 +0200 [thread overview]
Message-ID: <CAMHZB6FoEidThM+jz2FQuEuTwRUha3-uvUyEDVy2tetXBANmRg@mail.gmail.com> (raw)
In-Reply-To: <CANeU7QnZQqqxwJ=UjeVa4WunHjwFFdc3KBaAZriwesZXbxo8kA@mail.gmail.com>
On Sun, Aug 6, 2017 at 2:09 AM, Christopher Li <sparse@chrisli.org> wrote:
> On Sat, Aug 5, 2017 at 7:04 PM, Luc Van Oostenryck
> <luc.vanoostenryck@gmail.com> wrote:
>> No I only forgot to change [PATCH v3 0/5] into [PATCH v4 0/5] while copy pasting
>> the cover letter.
>>
>> cfr: http://marc.info/?l=linux-sparse&m=150188507213269&w=4
>>
>
> Do you think I need adjustment or the current version on sparse-next
> is fine? I already rebase to master.
No no. It's fine so.
> The base of your branch is not fast forward to master.
Yes, my branches often don't if there are some other patches but
the branching point is usually quite recent and the merge trivial.
-- Luc
next prev parent reply other threads:[~2017-08-06 1:07 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 ` [PATCH v3 0/5] fix list corruption with recursive remove_usage() Luc Van Oostenryck
2017-08-05 0:24 ` 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 [this message]
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=CAMHZB6FoEidThM+jz2FQuEuTwRUha3-uvUyEDVy2tetXBANmRg@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).