linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Eric Biggers <ebiggers@google.com>
Cc: linux-ext4@vger.kernel.org, Jan Kara <jack@suse.cz>,
	Andreas Gruenbacher <agruenba@redhat.com>
Subject: Re: [PATCH 5/5] mbcache: document that "find" functions only return reusable entries
Date: Sat, 3 Dec 2016 15:56:05 -0500	[thread overview]
Message-ID: <20161203205605.3ar5m5ax2kyoitwm@thunk.org> (raw)
In-Reply-To: <1480227481-98535-5-git-send-email-ebiggers@google.com>

On Sat, Nov 26, 2016 at 10:18:01PM -0800, Eric Biggers wrote:
> mb_cache_entry_find_first() and mb_cache_entry_find_next() only return
> cache entries with the 'e_reusable' bit set.  This should be documented.
> 
> Signed-off-by: Eric Biggers <ebiggers@google.com>

Thanks, applied.

					- Ted

  parent reply	other threads:[~2016-12-03 20:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-27  6:17 [PATCH 1/5] mbcache: correctly handle 'e_referenced' bit Eric Biggers
2016-11-27  6:17 ` [PATCH 2/5] mbcache: don't BUG() if entry cache cannot be allocated Eric Biggers
2016-11-28 12:09   ` Jan Kara
2016-12-03 20:30   ` Theodore Ts'o
2016-11-27  6:17 ` [PATCH 3/5] mbcache: remove unnecessary module_get/module_put Eric Biggers
2016-11-28 13:12   ` Jan Kara
2016-12-03 20:41   ` Theodore Ts'o
2016-11-27  6:18 ` [PATCH 4/5] mbcache: use consistent type for entry count Eric Biggers
2016-11-28 13:18   ` Jan Kara
2016-12-03 20:54   ` Theodore Ts'o
2016-11-27  6:18 ` [PATCH 5/5] mbcache: document that "find" functions only return reusable entries Eric Biggers
2016-11-28 13:19   ` Jan Kara
2016-12-03 20:56   ` Theodore Ts'o [this message]
2016-11-28 10:44 ` [PATCH 1/5] mbcache: correctly handle 'e_referenced' bit Jan Kara
2016-11-28 17:32   ` Eric Biggers
2016-12-03 20:28 ` Theodore Ts'o

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=20161203205605.3ar5m5ax2kyoitwm@thunk.org \
    --to=tytso@mit.edu \
    --cc=agruenba@redhat.com \
    --cc=ebiggers@google.com \
    --cc=jack@suse.cz \
    --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).