From: David Sterba <dsterba@suse.cz>
To: Alexandru Moise <00moses.alexander00@gmail.com>
Cc: clm@fb.com, jbacik@fb.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: memset cur_trans->delayed_refs to zero
Date: Tue, 22 Sep 2015 15:24:37 +0200 [thread overview]
Message-ID: <20150922132437.GE12815@suse.cz> (raw)
In-Reply-To: <20150922131936.GA1757@gmail.com>
On Tue, Sep 22, 2015 at 04:19:36PM +0300, Alexandru Moise wrote:
> Alright, do you want me to resend it with the different subject tag
> or shall I just keep that in mind for future patches?
No need to resend.
next prev parent reply other threads:[~2015-09-22 13:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 14:24 [PATCH] btrfs: memset cur_trans->delayed_refs to zero Alexandru Moise
2015-09-22 13:04 ` David Sterba
2015-09-22 13:19 ` Alexandru Moise
2015-09-22 13:24 ` David Sterba [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-07 13:45 Alexandru Moise
2015-09-07 14:01 ` David Sterba
2015-09-07 14:23 ` Alexandru Moise
2015-09-06 12:25 Alexandru Moise
2015-09-07 12:24 ` David Sterba
2015-09-07 13:44 ` Alexandru Moise
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=20150922132437.GE12815@suse.cz \
--to=dsterba@suse.cz \
--cc=00moses.alexander00@gmail.com \
--cc=clm@fb.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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).