From: "Theodore Ts'o" <tytso@mit.edu>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: fstests@vger.kernel.org, Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH] android-xfstests: create loopback device nodes in standard location
Date: Sat, 29 Apr 2017 12:41:24 -0400 [thread overview]
Message-ID: <20170429164124.byuracv4ud3n4435@thunk.org> (raw)
In-Reply-To: <20170311005632.130135-1-ebiggers3@gmail.com>
On Fri, Mar 10, 2017 at 04:56:32PM -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Android creates loopback device nodes in /dev/block/, where they can't
> be found by losetup. Create them in /dev/ too so that losetup can find
> them. This stops tests using loopback devices, e.g. generic/361 and
> shared/298, from failing.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Applied, thanks.
- Ted
prev parent reply other threads:[~2017-04-29 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 0:56 [PATCH] android-xfstests: create loopback device nodes in standard location Eric Biggers
2017-04-27 18:17 ` Eric Biggers
2017-04-29 16:41 ` Theodore Ts'o [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=20170429164124.byuracv4ud3n4435@thunk.org \
--to=tytso@mit.edu \
--cc=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=fstests@vger.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