From: "Theodore Ts'o" <tytso@mit.edu>
To: Andreas Dilger <adilger@whamcloud.com>
Cc: linux-ext4@vger.kernel.org, Li Dongyang <dongyangli@ddn.com>
Subject: Re: [PATCH] debugfs: allow <inode> for ncheck
Date: Fri, 12 Aug 2022 21:12:10 -0400 [thread overview]
Message-ID: <Yvb6anaiE6p/pzux@mit.edu> (raw)
In-Reply-To: <20220301041031.74615-1-adilger@whamcloud.com>
On Mon, Feb 28, 2022 at 09:10:31PM -0700, Andreas Dilger wrote:
> If the arg string is of the form <ino>, allow it for ncheck.
> Improve the error message, use "Invalid inode number" instead
> of "Bad inode", which implies the inode content being bad.
>
> Signed-off-by: Li Dongyang <dongyangli@ddn.com>
> Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Applied, thanks!
- Ted
prev parent reply other threads:[~2022-08-13 1:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 4:10 [PATCH] debugfs: allow <inode> for ncheck Andreas Dilger
2022-08-13 1:12 ` 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=Yvb6anaiE6p/pzux@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@whamcloud.com \
--cc=dongyangli@ddn.com \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).