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 fixes (next)
Date: Tue, 19 Jul 2016 13:18:40 -0700 [thread overview]
Message-ID: <20160719201840.GA1222@www.outflux.net> (raw)
Hi,
Please pull these lkdtm fixes for next.
Thanks!
-Kees
The following changes since commit 45c7d71e1675f7ef73acab2738dd6f220005aa2a:
Merge tag 'lkdtm-next' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux into char-misc-testing (2016-07-17 08:29:53 +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 a37830b79957f8c48284c9ca16f399e2edb6b2ba:
lkdtm: fix false positive warning from -Wmaybe-uninitialized (2016-07-19 13:16:32 -0700)
----------------------------------------------------------------
Silence a harmless compiler warning
----------------------------------------------------------------
Kees Cook (1):
lkdtm: fix false positive warning from -Wmaybe-uninitialized
drivers/misc/lkdtm_usercopy.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Kees Cook
Brillo & Chrome OS Security
reply other threads:[~2016-07-19 20:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160719201840.GA1222@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®