From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] lkdtm updates for next, part 2
Date: Tue, 15 Aug 2017 18:12:32 -0700 [thread overview]
Message-ID: <20170816011232.GA11120@kroah.com> (raw)
In-Reply-To: <20170815194316.GA31327@beast>
On Tue, Aug 15, 2017 at 12:43:16PM -0700, Kees Cook wrote:
> Hi Greg,
>
> Please pull these additional lkdtm changes for next.
>
> Thanks!
>
> -Kees
>
> The following changes since commit c7fea48876773603721f545f8c1a2f894291ef85:
>
> lkdtm: Provide timing tests for atomic_t vs refcount_t (2017-07-26 14:38:04 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/lkdtm-next-part2
Pulled and pushed out, thanks.
greg k-h
prev parent reply other threads:[~2017-08-16 1:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 19:43 [GIT PULL] lkdtm updates for next, part 2 Kees Cook
2017-08-16 1:12 ` 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=20170816011232.GA11120@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=keescook@chromium.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).