All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>
Subject: [git pull] device mapper fix for 4.18-rc6
Date: Fri, 20 Jul 2018 15:14:07 -0400	[thread overview]
Message-ID: <20180720191407.GA11868@redhat.com> (raw)

Hi Linus,

The following change since commit 021c91791a5e7e85c567452f1be3e4c2c6cb6063:

  Linux 4.18-rc3 (2018-07-01 16:04:53 -0700)

is available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-4.18/dm-fixes-2

for you to fetch up to d284f8248c72d0cb36a930920e60592eb455cd0d:

  dm writecache: support optional offset for start of device (2018-07-02 16:14:02 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
- Fix DM writecache target to allow an optional offset to the start of
  the data and metadata area.  This allows userspace tools (e.g. LVM2)
  to place a header and metadata at the front of the writecache device
  for its use.

----------------------------------------------------------------
Mikulas Patocka (1):
      dm writecache: support optional offset for start of device

 Documentation/device-mapper/writecache.txt |  2 ++
 drivers/md/dm-writecache.c                 | 43 ++++++++++++++++++++----------
 2 files changed, 31 insertions(+), 14 deletions(-)

             reply	other threads:[~2018-07-20 19:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20 19:14 Mike Snitzer [this message]
2018-07-20 21:25 ` [git pull] device mapper fix for 4.18-rc6 Linus Torvalds
2018-07-20 22:40   ` Mike Snitzer
2018-07-24 15:18     ` Mikulas Patocka
2018-07-24 15:30       ` David Teigland

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=20180720191407.GA11868@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=mpatocka@redhat.com \
    --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.