From: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 0/2] HSI: Fine-tuning for three function implementations
Date: Mon, 1 May 2017 11:08:10 +0200 [thread overview]
Message-ID: <20170501090809.xwvmf6bdkbj5dkze@earth> (raw)
In-Reply-To: <52f7db50-a3a0-6bc5-a39f-1d235a5945cd@users.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
Hi,
On Tue, Apr 25, 2017 at 02:43:25PM +0200, SF Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Tue, 25 Apr 2017 14:32:10 +0200
>
> Two update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (2):
> Use kcalloc() in hsi_register_board_info()
> core: Use kcalloc() in two functions
>
> drivers/hsi/hsi_boardinfo.c | 2 +-
> drivers/hsi/hsi_core.c | 7 +++----
> 2 files changed, 4 insertions(+), 5 deletions(-)
Thanks for your patchset. We are currently in the merge
window and your patch will appear in linux-next once
4.12-rc1 has been tagged by Linus Torvalds.
Until then I queued it into this branch:
https://git.kernel.org/cgit/linux/kernel/git/sre/linux-hsi.git/log/?h=for-next-next
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-05-01 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 12:43 [PATCH 0/2] HSI: Fine-tuning for three function implementations SF Markus Elfring
2017-04-25 12:45 ` [PATCH 1/2] HSI: Use kcalloc() in hsi_register_board_info() SF Markus Elfring
2017-04-25 12:46 ` [PATCH 2/2] HSI: core: Use kcalloc() in two functions SF Markus Elfring
2017-05-01 9:08 ` Sebastian Reichel [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=20170501090809.xwvmf6bdkbj5dkze@earth \
--to=sebastian.reichel@collabora.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).