public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: ltp@lists.linux.it
Subject: [LTP] LTP: mount02 was expected EINVAL(22) but got ENOENT(2): No such file or directory
Date: Thu, 18 Apr 2019 08:24:54 +0100	[thread overview]
Message-ID: <20190418072454.GD2217@ZenIV.linux.org.uk> (raw)
In-Reply-To: <5CB823D9.8050902@cn.fujitsu.com>

On Thu, Apr 18, 2019 at 03:14:33PM +0800, Xiao Yang wrote:

> Does you or Al Viro plan to replace ENOENT with ENOTBLK recently?
> It seems that ENOENT still exists on v5.1-rc5.

I am; I'm sorting the next pile of mount patches at the moment,
and fix for that is going to be in the very beginning.

  reply	other threads:[~2019-04-18  7:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 13:47 [LTP] LTP: mount02 was expected EINVAL(22) but got ENOENT(2): No such file or directory Naresh Kamboju
2019-03-13 15:29 ` Jan Stancek
2019-03-14  5:18   ` Naresh Kamboju
2019-03-14  8:23     ` Jan Stancek
2019-04-18  7:14       ` Xiao Yang
2019-04-18  7:24         ` Al Viro [this message]
2019-04-18  7:35           ` Xiao Yang

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=20190418072454.GD2217@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=ltp@lists.linux.it \
    /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