From: Jens Axboe <axboe@fb.com>
To: Minfei Huang <mnghuan@gmail.com>, <ming.lei@canonical.com>,
<viro@zeniv.linux.org.uk>, <jmoyer@redhat.com>,
<sagig@mellanox.com>, <mszeredi@suse.cz>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] loop: Make user notify for adding loop device failed
Date: Tue, 12 Jul 2016 16:17:51 -0700 [thread overview]
Message-ID: <57857A9F.8080700@fb.com> (raw)
In-Reply-To: <1465265115-12479-1-git-send-email-mnghuan@gmail.com>
On 06/06/2016 07:05 PM, Minfei Huang wrote:
> There is no error number returned if loop driver fails in function
> alloc_disk to add new loop device. Add a correct error number to make
> user notify in this case.
Sorry about the delay, vacation got in the way. Added for 4.8, thanks.
--
Jens Axboe
prev parent reply other threads:[~2016-07-12 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 2:05 [PATCH] loop: Make user notify for adding loop device failed Minfei Huang
2016-06-07 2:49 ` Ming Lei
2016-06-07 13:42 ` Jeff Moyer
2016-07-12 23:17 ` 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=57857A9F.8080700@fb.com \
--to=axboe@fb.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=mnghuan@gmail.com \
--cc=mszeredi@suse.cz \
--cc=sagig@mellanox.com \
--cc=viro@zeniv.linux.org.uk \
/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