linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Lyakas <alex@zadara.com>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs fixes for 4.15-rc2
Date: Mon, 18 Feb 2019 12:37:49 +0200	[thread overview]
Message-ID: <CAOcd+r2vJfDQcF+zqZStHMiz4PYw1irsvHYK=PjUJ5nYuUffug@mail.gmail.com> (raw)
In-Reply-To: <cover.1511980478.git.dsterba@suse.com>

Hi David,

>   Btrfs: incremental send, fix wrong unlink path after renaming file (2017-11-28 17:15:30 +0100)
>
> ----------------------------------------------------------------
> David Sterba (2):
>       btrfs: add missing device::flush_bio puts
Is there a reason that this one should not be tagged as "stable"? At
least the missing bio_put in  free_fs_devices is not an error case,
and would happen every time.

Thanks,
Alex.

  parent reply	other threads:[~2019-02-18 10:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 19:28 [GIT PULL] Btrfs fixes for 4.15-rc2 David Sterba
2017-11-29 22:31 ` Linus Torvalds
2017-11-30 14:41   ` David Sterba
2019-02-18 10:37 ` Alex Lyakas [this message]
2019-02-18 16:15   ` David Sterba

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='CAOcd+r2vJfDQcF+zqZStHMiz4PYw1irsvHYK=PjUJ5nYuUffug@mail.gmail.com' \
    --to=alex@zadara.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@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).