Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: Mark Fasheh <mfasheh@suse.de>
Cc: linux-btrfs@vger.kernel.org, Chris Mason <clm@fb.com>
Subject: Re: Missing dedupe/locking patch in integration-4.2 tree?
Date: Tue, 11 Aug 2015 21:42:10 +0200	[thread overview]
Message-ID: <55CA5012.7070709@googlemail.com> (raw)
In-Reply-To: <20150811185842.GN7507@wotan.suse.de>

On 08/11/15 20:58, Mark Fasheh wrote:
> On Fri, Aug 07, 2015 at 10:11:46AM +0200, Holger Hoffstätte wrote:
>>
>> Mark's patch titled
>>
>>   "[PATCH 3/5] btrfs: fix clone / extent-same deadlocks" [1]
>>
>> from his "btrfs: dedupe fixes, features" series is missing from the integration-4.2 tree and 4.2-rc5, where it still applies cleanly (as of 5 mins ago).
>>
>> Any particular reason why this was silently dropped?
> 
> Same question here, I noticed this shortly after everything went upstream
> and was planning a resend but it would be great if you could tell us whether
> something was wrong with the patch or if it just got lost in the shuffle (no
> big deal).
> 	--Mark

I saw this morning that it went into integration-4.3:

https://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git/commit/?h=integration-4.3&id=293a8489f300536dc6d996c35a6ebb89aa03bab2

So probably just an oversight.

-h


  reply	other threads:[~2015-08-11 19:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07  8:11 Missing dedupe/locking patch in integration-4.2 tree? Holger Hoffstätte
2015-08-11 18:58 ` Mark Fasheh
2015-08-11 19:42   ` Holger Hoffstätte [this message]
2015-08-11 21:00     ` Mark Fasheh

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=55CA5012.7070709@googlemail.com \
    --to=holger.hoffstaette@googlemail.com \
    --cc=clm@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mfasheh@suse.de \
    /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