From: Christoph Hellwig <hch@lst.de>
To: mwilck@suse.com
Cc: Jens Axboe <axboe@kernel.dk>, Mike Snitzer <snitzer@redhat.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Christoph Hellwig <hch@lst.de>,
Alasdair G Kergon <agk@redhat.com>
Subject: Re: [dm-devel] [PATCH v2] dm: avoid filesystem lookup in dm_get_dev_t()
Date: Thu, 21 Jan 2021 18:53:39 +0100 [thread overview]
Message-ID: <20210121175339.GA828@lst.de> (raw)
In-Reply-To: <20210121175056.20078-1-mwilck@suse.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
Mike, Jens - can we make sure this goes in before branching off the
block branch for 5.12? I have some work pending that would otherwise
conflict.
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: mwilck@suse.com
Cc: Christoph Hellwig <hch@lst.de>, Mike Snitzer <snitzer@redhat.com>,
Hannes Reinecke <hare@suse.de>,
Alasdair G Kergon <agk@redhat.com>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, dm-devel@redhat.com
Subject: Re: [PATCH v2] dm: avoid filesystem lookup in dm_get_dev_t()
Date: Thu, 21 Jan 2021 18:53:39 +0100 [thread overview]
Message-ID: <20210121175339.GA828@lst.de> (raw)
In-Reply-To: <20210121175056.20078-1-mwilck@suse.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
Mike, Jens - can we make sure this goes in before branching off the
block branch for 5.12? I have some work pending that would otherwise
conflict.
next prev parent reply other threads:[~2021-01-21 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 17:50 [dm-devel] [PATCH v2] dm: avoid filesystem lookup in dm_get_dev_t() mwilck
2021-01-21 17:50 ` mwilck
2021-01-21 17:53 ` Christoph Hellwig [this message]
2021-01-21 17:53 ` Christoph Hellwig
2021-01-21 17:57 ` [dm-devel] " Mike Snitzer
2021-01-21 17:57 ` Mike Snitzer
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=20210121175339.GA828@lst.de \
--to=hch@lst.de \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=mwilck@suse.com \
--cc=snitzer@redhat.com \
/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.