From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH 0/3] lkdtm: fixes for v4.8-rc1
Date: Wed, 31 Aug 2016 17:00:10 +0200 [thread overview]
Message-ID: <20160831150010.GA26702@kroah.com> (raw)
In-Reply-To: <CAGXu5j+PZG-BJ+tj1p9WUbdBw0rey_f68tMi155u2Jdfde8zEQ@mail.gmail.com>
On Wed, Aug 31, 2016 at 10:46:00AM -0400, Kees Cook wrote:
> On Wed, Aug 31, 2016 at 7:15 AM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Fri, Aug 05, 2016 at 02:25:50PM -0700, Kees Cook wrote:
> >> Hi Greg!
> >>
> >> As requested, here's a patch series for 3 small fixes for lkdtm for v4.8
> >> (instead of as a pull request).
> >>
> >> Thanks!
> >
> > Sorry for the delay.
> >
> > I think I'm all caught up on lkdtm patches now, right? If not, can you
> > please resend anything that I have missed?
>
> I think Linus may have taken some of these already; please
> double-check, but yes, that's it for lkdtm on v4.8. Thanks!
Yes, he took 2, only one applied to my local tree.
thanks,
greg k-h
prev parent reply other threads:[~2016-08-31 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 21:25 [PATCH 0/3] lkdtm: fixes for v4.8-rc1 Kees Cook
2016-08-05 21:25 ` [PATCH 1/3] lkdtm: fix false positive warning from -Wmaybe-uninitialized Kees Cook
2016-08-05 21:25 ` [PATCH 2/3] lkdtm: Fix targets for objcopy usage Kees Cook
2016-08-05 21:25 ` [PATCH 3/3] lkdtm: Mark lkdtm_rodata_do_nothing() notrace Kees Cook
2016-08-31 11:15 ` [PATCH 0/3] lkdtm: fixes for v4.8-rc1 Greg Kroah-Hartman
2016-08-31 14:46 ` Kees Cook
2016-08-31 15:00 ` Greg Kroah-Hartman [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=20160831150010.GA26702@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.