From: Tyler Hicks <tyhicks@canonical.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>,
ecryptfs@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 0/3] eCryptfs: Adjustments for several function implementations
Date: Fri, 13 Oct 2017 21:29:42 -0400 [thread overview]
Message-ID: <66a69c57-4dff-bed7-75e8-2ebb92f20909@canonical.com> (raw)
In-Reply-To: <56e0a575-2a9e-120f-6a22-96d9fa4b151e@users.sourceforge.net>
[-- Attachment #1.1: Type: text/plain, Size: 927 bytes --]
On 08/19/2017 12:54 PM, SF Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Sat, 19 Aug 2017 18:15:14 +0200
>
> Some update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (3):
> Delete 21 error messages for a failed memory allocation
> Return an error code only as a constant in ecryptfs_add_global_auth_tok()
> Adjust four checks for null pointers
Hello! I'm sorry for just now getting to these patches. All three look
fine to me. I'll get them into 4.15.
Tyler
>
> fs/ecryptfs/crypto.c | 22 +++-------------------
> fs/ecryptfs/inode.c | 3 ---
> fs/ecryptfs/keystore.c | 46 +++++++++++-----------------------------------
> fs/ecryptfs/messaging.c | 6 ------
> fs/ecryptfs/miscdev.c | 6 +-----
> fs/ecryptfs/mmap.c | 2 --
> 6 files changed, 15 insertions(+), 70 deletions(-)
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2017-10-14 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 16:54 SF Markus Elfring
2017-08-19 16:55 ` [PATCH 1/3] ecryptfs: Delete 21 error messages for a failed memory allocation SF Markus Elfring
2017-08-19 16:56 ` [PATCH 2/3] ecryptfs: Return an error code only as a constant in ecryptfs_add_global_auth_tok() SF Markus Elfring
2017-08-19 16:57 ` [PATCH 3/3] ecryptfs: Adjust four checks for null pointers SF Markus Elfring
2017-10-14 1:29 ` Tyler Hicks [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=66a69c57-4dff-bed7-75e8-2ebb92f20909@canonical.com \
--to=tyhicks@canonical.com \
--cc=ecryptfs@vger.kernel.org \
--cc=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®