From: tytso@mit.edu
To: brookxu <brookxu.cn@gmail.com>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 1/2] ext4: rename journal_dev to s_journal_dev inside ext4_sb_info
Date: Fri, 7 Aug 2020 01:05:56 -0400 [thread overview]
Message-ID: <20200807050556.GT7657@mit.edu> (raw)
In-Reply-To: <74c2a122-5a6c-ac97-614a-043038d61623@gmail.com>
On Wed, Jul 29, 2020 at 02:19:20PM +0800, brookxu wrote:
> Rename journal_dev to s_journal_dev inside ext4_sb_info, keep
> the naming rules consistent with other variables, which is
> convenient for code reading and writing.
>
> Signed-off-by: Chunguang Xu <brookxu@tencent.com>
This patch series is badly white-space damaged. Can you please resend
it using a different e-mail client which doesn't mangle whitespace?
Please see:
https://www.kernel.org/doc/html/latest/process/email-clients.html
- Ted
next prev parent reply other threads:[~2020-08-07 5:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 6:19 [PATCH 1/2] ext4: rename journal_dev to s_journal_dev inside ext4_sb_info brookxu
2020-07-29 20:02 ` Andreas Dilger
2020-08-07 5:05 ` tytso [this message]
2020-08-07 6:24 ` brookxu
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=20200807050556.GT7657@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=brookxu.cn@gmail.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).