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, Christoph Hellwig <hch@lst.de>,
	Alasdair G Kergon <agk@redhat.com>
Subject: [git pull] device mapper post-merge changes for 4.12
Date: Tue, 2 May 2017 15:05:21 -0400	[thread overview]
Message-ID: <20170502190520.GA79914@redhat.com> (raw)

Hi Linus,

Here are some changes from Christoph that needed to be rebased ontop of
changes that were already merged into the 'tags/for-4.12/dm-changes'.
In addition, these changes depend on the 'for-4.12/block' changes that
you've already merged.  So once you've pulled 'tags/for-4.12/dm-changes'
please then consider pulling these changes.

The following changes since commit 7e25a7606147bfe29a7421ff2cb332b07d3cee3a:

  Merge branch 'dm-4.12' into dm-4.12-post-merge (2017-05-01 18:18:04 -0400)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-4.12/dm-post-merge-changes

for you to fetch changes up to 412445acb6cad4cef026daae37c4765fb9942c60:

  dm: introduce a new DM_MAPIO_KILL return value (2017-05-01 18:19:03 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
- Cleanups to request-based DM and DM multipath from Christoph that
  prepare for his block core error code type checking improvements.

----------------------------------------------------------------
Christoph Hellwig (3):
      dm mpath: merge do_end_io into multipath_end_io
      dm rq: change ->rq_end_io calling conventions
      dm: introduce a new DM_MAPIO_KILL return value

 drivers/md/dm-mpath.c         | 54 +++++++++++++++++--------------------------
 drivers/md/dm-rq.c            | 29 ++++++++++++-----------
 drivers/md/dm-target.c        |  2 +-
 include/linux/device-mapper.h |  2 ++
 4 files changed, 39 insertions(+), 48 deletions(-)

                 reply	other threads:[~2017-05-02 19:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170502190520.GA79914@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=hch@lst.de \
    --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.