From: David Sterba <dsterba@suse.cz>
To: Chengguang Xu <cgxu519@mykernel.net>
Cc: clm@fb.com, josef@toxicpanda.com, dsterba@suse.com,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 1/3] btrfs: remove unnecessary hash_init()
Date: Thu, 10 Oct 2019 18:58:12 +0200 [thread overview]
Message-ID: <20191010165811.GZ2751@twin.jikos.cz> (raw)
In-Reply-To: <20191010075958.28346-1-cgxu519@mykernel.net>
On Thu, Oct 10, 2019 at 03:59:56PM +0800, Chengguang Xu wrote:
> DEFINE_HASHTABLE itself has already included initialization code,
> we don't have to call hash_init() again, so remove it.
>
> Signed-off-by: Chengguang Xu <cgxu519@mykernel.net>
1-3 added to misc-next, with minor updates. Thanks.
prev parent reply other threads:[~2019-10-10 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 7:59 [PATCH v2 1/3] btrfs: remove unnecessary hash_init() Chengguang Xu
2019-10-10 7:59 ` [PATCH v2 2/3] btrfs: code cleanup for compression type Chengguang Xu
2019-10-10 7:59 ` [PATCH v2 3/3] btrfs: using enum to replace macro Chengguang Xu
2019-10-10 16:58 ` David Sterba [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=20191010165811.GZ2751@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=cgxu519@mykernel.net \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@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).