From: kbusch@kernel.org (Keith Busch)
Subject: Issue with namespace delete
Date: Thu, 16 May 2019 10:03:00 -0600 [thread overview]
Message-ID: <20190516160259.GD23416@localhost.localdomain> (raw)
In-Reply-To: <20190516155356.GA26104@infradead.org>
On Thu, May 16, 2019@08:53:56AM -0700, Christoph Hellwig wrote:
> We could try something like the changes below, although they are
> completely untested for now and will need to be split up into
> a few patches:
Looks correct to me.
next prev parent reply other threads:[~2019-05-16 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 1:23 Issue with namespace delete Heitke, Kenneth
2019-05-16 15:11 ` Keith Busch
2019-05-16 15:53 ` Christoph Hellwig
2019-05-16 16:03 ` Keith Busch [this message]
2019-05-16 17:49 ` Heitke, Kenneth
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=20190516160259.GD23416@localhost.localdomain \
--to=kbusch@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox