From: axboe@kernel.dk (Jens Axboe)
Subject: [GIT PULL] nvme one-liner fix for 4.17
Date: Tue, 29 May 2018 12:56:00 -0600 [thread overview]
Message-ID: <abb5d799-8889-711c-2dce-7d021648e57b@kernel.dk> (raw)
In-Reply-To: <20180529185148.GA30983@infradead.org>
On 5/29/18 12:51 PM, Christoph Hellwig wrote:
> Hi Jens,
>
> below is a one-liner fix from Max that unbreaks T10-DIF support, which
> got broken in 4.15.
>
> The following changes since commit eedffa28c9b00ca2dcb4d541b5a530f4c917052d:
>
> loop: clear wb_err in bd_inode when detaching backing file (2018-05-21 12:36:03 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git nvme-4.17
>
> for you to fetch changes up to c97f414c54a255f4f05a50a2625efaeee406e134:
>
> nvme: fix extended data LBA supported setting (2018-05-29 20:29:16 +0200)
>
> ----------------------------------------------------------------
> Max Gurtovoy (1):
> nvme: fix extended data LBA supported setting
Pulled, thanks.
--
Jens Axboe
prev parent reply other threads:[~2018-05-29 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 18:51 [GIT PULL] nvme one-liner fix for 4.17 Christoph Hellwig
2018-05-29 18:56 ` Jens Axboe [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=abb5d799-8889-711c-2dce-7d021648e57b@kernel.dk \
--to=axboe@kernel.dk \
/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).