From: Kees Cook <keescook@chromium.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: [PULL] lkdtm update (next)
Date: Fri, 15 Jul 2016 16:16:19 -0700 [thread overview]
Message-ID: <20160715231619.GA18804@www.outflux.net> (raw)
Hi,
Please pull these lkdtm fixes for next.
Thanks!
-Kees
The following changes since commit 80f76319634fc62befd440b328042dbd54e3b6f8:
Merge tag 'stm-for-greg-20160714' of git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm into char-misc-next (2016-07-15 14:19:11 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/lkdtm-next
for you to fetch changes up to 6d2e91a662256fd88ec0505567a59d21094ed415:
lkdtm: silence warnings about function declarations (2016-07-15 16:14:45 -0700)
----------------------------------------------------------------
fixes for lkdtm build warnings
----------------------------------------------------------------
Arnd Bergmann (1):
lkdtm: hide unused functions
Kees Cook (1):
lkdtm: silence warnings about function declarations
drivers/misc/lkdtm.h | 5 ++-
drivers/misc/lkdtm_bugs.c | 6 +---
drivers/misc/lkdtm_core.c | 72 ++++++++++++++++++++++---------------------
drivers/misc/lkdtm_heap.c | 6 +---
drivers/misc/lkdtm_perms.c | 6 +---
drivers/misc/lkdtm_rodata.c | 2 +-
drivers/misc/lkdtm_usercopy.c | 4 +--
7 files changed, 46 insertions(+), 55 deletions(-)
--
Kees Cook
Brillo & Chrome OS Security
next reply other threads:[~2016-07-15 23:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 23:16 Kees Cook [this message]
2016-07-16 23:30 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2016-07-07 18:14 Kees Cook
2016-07-12 18:42 ` Kees Cook
2016-07-13 1:00 ` Greg KH
2016-07-13 3:03 ` Kees Cook
2016-07-14 3:00 ` Greg KH
2016-06-10 23:02 Kees Cook
2016-06-11 0:00 ` Greg KH
2016-06-11 0:38 ` Kees Cook
2016-06-11 5:09 ` Greg KH
2016-03-01 22:31 Kees Cook
2016-03-02 0:53 ` Greg KH
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=20160715231619.GA18804@www.outflux.net \
--to=keescook@chromium.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.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®