From: "Theodore Ts'o" <tytso@mit.edu>
To: Jakub Wilk <jwilk@jwilk.net>
Cc: "Theodore Ts'o" <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH e2fsprogs] e4crypt: fix spurious "Success" error message
Date: Thu, 18 Apr 2024 10:39:17 -0400 [thread overview]
Message-ID: <171345110558.3373948.7028509495340755466.b4-ty@mit.edu> (raw)
In-Reply-To: <20231227080805.6801-1-jwilk@jwilk.net>
On Wed, 27 Dec 2023 09:08:05 +0100, Jakub Wilk wrote:
> Before:
>
> # e4crypt set_policy 0000000000000000 /dev/null
> /dev/null is not a directory
> /dev/null: Success
>
> After:
>
> [...]
Applied, thanks!
[1/1] e4crypt: fix spurious "Success" error message
commit: 1275bbaaea7ffd42346789f945c2f4dcddbfbbc8
Best regards,
--
Theodore Ts'o <tytso@mit.edu>
prev parent reply other threads:[~2024-04-18 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 8:08 [PATCH e2fsprogs] e4crypt: fix spurious "Success" error message Jakub Wilk
2024-04-18 14:39 ` 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=171345110558.3373948.7028509495340755466.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=jwilk@jwilk.net \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).