From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Cc: NeilBrown <neilb@suse.de>,
linux-nfs@vger.kernel.org, Jeff Layton <jlayton@kernel.org>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Subject: Re: [LTP] [PATCH 1/1] nfs08.sh: Skip on vfat
Date: Fri, 5 May 2023 19:45:53 +0200 [thread overview]
Message-ID: <20230505174553.GA37086@pevik> (raw)
In-Reply-To: <20230502151348.3677809-1-pvorel@suse.cz>
Hi,
> vfat does not see '2' on various distros:
> * openSUSE Tumbleweed 20230427 (kernel 6.2.12-1-default, nfs-utils 2.6.3,
> mkfs.fat 4.2 (2021-01-31))
> * Debian 12 bookworm (kernel 6.1.0-6-amd64, nfs-utils 2.6.2, mkfs.fat 4.2
> (2021-01-31))
Again, because we don't test on vfat in the end, I did not merge this and I'm
setting this in patchwork as rejected.
Kind regards,
Petr
> NOTE: on it fails completely (on all filesystems) on Debian 11 bullseye
> (kernel 5.10.0-8-amd64, nfs-utils 1.3.3, mkfs.fat 4.2 (2021-01-31)) -
> likely due 1.3.3, thus skip the test completely.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2023-05-05 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 15:13 [LTP] [PATCH 1/1] nfs08.sh: Skip on vfat Petr Vorel
2023-05-05 17:45 ` Petr Vorel [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=20230505174553.GA37086@pevik \
--to=pvorel@suse.cz \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=neilb@suse.de \
/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