From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v4 2/2] btrfs: Reformat btrfs_tree.h comments
Date: Thu, 16 Apr 2020 12:20:21 +0200 [thread overview]
Message-ID: <20200416102021.GH5920@twin.jikos.cz> (raw)
In-Reply-To: <20200415084113.64378-3-wqu@suse.com>
On Wed, Apr 15, 2020 at 04:41:13PM +0800, Qu Wenruo wrote:
> Since we're here, modify btrfs_tree.h to follow the latest comment
> style.
Well, the point was to make the changes when moving the code so it's not
split into two patches, but this patch seems to update more code so it's
probably fine to have them separate.
next prev parent reply other threads:[~2020-04-16 10:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 8:41 [PATCH v4 0/2] btrfs: Reformat and make btrfs_tree.h self-contained Qu Wenruo
2020-04-15 8:41 ` [PATCH v4 1/2] btrfs: Move on-disk structure definition to btrfs_tree.h Qu Wenruo
2020-04-21 11:31 ` Christoph Hellwig
2020-04-21 11:41 ` Qu Wenruo
2020-04-24 20:24 ` David Sterba
2020-04-25 7:14 ` Christoph Hellwig
2020-04-25 7:25 ` Qu Wenruo
2020-04-30 7:29 ` Qu Wenruo
2020-04-23 11:32 ` kbuild test robot
2020-04-15 8:41 ` [PATCH v4 2/2] btrfs: Reformat btrfs_tree.h comments Qu Wenruo
2020-04-16 10:20 ` David Sterba [this message]
2020-04-16 12:54 ` David Sterba
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=20200416102021.GH5920@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.com \
/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).