From: David Sterba <dsterba@suse.cz>
To: torvalds@linux-foundation.org
Cc: clm@fb.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, David Sterba <DSterba@suse.com>
Subject: Re: [GIT PULL] Btrfs fixes for 4.18-rc1
Date: Sun, 24 Jun 2018 17:22:41 +0200 [thread overview]
Message-ID: <20180624152240.GD24375@suse.cz> (raw)
In-Reply-To: <cover.1529853141.git.dsterba@suse.com>
On Sun, Jun 24, 2018 at 05:19:58PM +0200, David Sterba wrote:
> The following changes since commit ac0b4145d662a3b9e34085dea460fb06ede9b69b:
>
> btrfs: scrub: Don't use inode pages for device replace (2018-06-11 15:59:14 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-4.18-rc1
The signed tag is there too, I forgot to update it in the mail, sorry:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-4.18-rc1-tag
> for you to fetch changes up to c5b4a50b74018b3677098151ec5f4fce07d5e6a0:
>
> Btrfs: fix return value on rename exchange failure (2018-06-22 12:59:08 +0200)
>
> ----------------------------------------------------------------
> Filipe Manana (2):
> Btrfs: fix physical offset reported by fiemap for inline extents
> Btrfs: fix return value on rename exchange failure
>
> Lu Fengqi (1):
> btrfs: fix invalid-free in btrfs_extent_same
>
> fs/btrfs/extent_io.c | 5 ++++-
> fs/btrfs/inode.c | 4 +++-
> fs/btrfs/ioctl.c | 10 +++++-----
> 3 files changed, 12 insertions(+), 7 deletions(-)
prev parent reply other threads:[~2018-06-24 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 15:19 [GIT PULL] Btrfs fixes for 4.18-rc1 David Sterba
2018-06-24 15:22 ` David Sterba [this message]
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=20180624152240.GD24375@suse.cz \
--to=dsterba@suse.cz \
--cc=DSterba@suse.com \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.