From: Jonathan Corbet <corbet@lwn.net>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
Theodore Ts'o <tytso@mit.edu>, Jaegeuk Kim <jaegeuk@kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Subject: Re: [PATCH] docs: f2fs: fix a broken table
Date: Mon, 22 Jun 2020 11:22:09 -0600 [thread overview]
Message-ID: <20200622112209.71990f9c@lwn.net> (raw)
In-Reply-To: <20200622171106.GA192855@gmail.com>
On Mon, 22 Jun 2020 10:11:06 -0700
Eric Biggers <ebiggers@kernel.org> wrote:
> Someone already sent out a fix for this:
> https://lkml.kernel.org/linux-doc/52f851cb5c9fd2ecae97deec7e168e66b8c295c3.1591137229.git.mchehab+huawei@kernel.org/
>
> Is it intentional that you're sending out a different fix rather than applying
> that one?
It wasn't, actually, I'm just finding myself more than usually challenged
these days.
That said, removing the table entirely seems ... excessive. It's not
terrible the way it is, or we could make it:
test_dummy_encryption[=%s]
if we really want to.
jon
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
linux-doc@vger.kernel.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [f2fs-dev] [PATCH] docs: f2fs: fix a broken table
Date: Mon, 22 Jun 2020 11:22:09 -0600 [thread overview]
Message-ID: <20200622112209.71990f9c@lwn.net> (raw)
In-Reply-To: <20200622171106.GA192855@gmail.com>
On Mon, 22 Jun 2020 10:11:06 -0700
Eric Biggers <ebiggers@kernel.org> wrote:
> Someone already sent out a fix for this:
> https://lkml.kernel.org/linux-doc/52f851cb5c9fd2ecae97deec7e168e66b8c295c3.1591137229.git.mchehab+huawei@kernel.org/
>
> Is it intentional that you're sending out a different fix rather than applying
> that one?
It wasn't, actually, I'm just finding myself more than usually challenged
these days.
That said, removing the table entirely seems ... excessive. It's not
terrible the way it is, or we could make it:
test_dummy_encryption[=%s]
if we really want to.
jon
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2020-06-22 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 13:39 [PATCH] docs: f2fs: fix a broken table Jonathan Corbet
2020-06-22 17:11 ` Eric Biggers
2020-06-22 17:11 ` [f2fs-dev] " Eric Biggers
2020-06-22 17:22 ` Jonathan Corbet [this message]
2020-06-22 17:22 ` Jonathan Corbet
2020-06-23 5:57 ` Mauro Carvalho Chehab
2020-06-23 5:57 ` [f2fs-dev] " Mauro Carvalho Chehab
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=20200622112209.71990f9c@lwn.net \
--to=corbet@lwn.net \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.