Linux FSCRYPT development
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: linux-fscrypt@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
	Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH] fscrypt: inline fscrypt_free_filename()
Date: Fri, 23 Jun 2017 20:02:50 -0400	[thread overview]
Message-ID: <20170624000250.kx7o7dwfun2akvw4@thunk.org> (raw)
In-Reply-To: <20170523011406.32718-1-ebiggers3@gmail.com>

On Mon, May 22, 2017 at 06:14:06PM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
> 
> fscrypt_free_filename() only needs to do a kfree() of crypto_buf.name,
> which works well as an inline function.  We can skip setting the various
> pointers to NULL, since no user cares about it (the name is always freed
> just before it goes out of scope).
> 
> Signed-off-by: Eric Biggers <ebiggers@google.com>

Thanks, applied.

					- Ted

      parent reply	other threads:[~2017-06-24  0:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23  1:14 [PATCH] fscrypt: inline fscrypt_free_filename() Eric Biggers
2017-05-23  6:01 ` David Gstir
2017-06-24  0:02 ` Theodore Ts'o [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=20170624000250.kx7o7dwfun2akvw4@thunk.org \
    --to=tytso@mit.edu \
    --cc=ebiggers3@gmail.com \
    --cc=ebiggers@google.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-fscrypt@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