From: David Howells <dhowells@redhat•com>
To: Baolin Wang <baolin.wang@linaro•org>
Cc: dhowells@redhat•com, davem@davemloft•net,
james.l.morris@oracle•com, serge@hallyn•com,
marc.dionne@auristor•com, dan.carpenter@oracle•com,
Jason@zx2c4•com, arnd@arndb•de, broonie@kernel•org,
keyrings@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-security-module@vger•kernel.org, netdev@vger•kernel.org
Subject: Re: [PATCH 0/3] Fix y2038 issues for security/keys subsystem
Date: Wed, 09 Aug 2017 09:28:43 +0100 [thread overview]
Message-ID: <4455.1502267323@warthog.procyon.org.uk> (raw)
In-Reply-To: <cover.1502246501.git.baolin.wang@linaro.org>
The rxrpc patch isn't part of the security/keys subsystem. I'll push it
to the network tree. The other two I'll push to James.
David
next prev parent reply other threads:[~2017-08-09 8:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 2:51 [PATCH 0/3] Fix y2038 issues for security/keys subsystem Baolin Wang
2017-08-09 2:51 ` [PATCH 1/3] security: keys: Replace time_t/timespec with time64_t Baolin Wang
2017-08-09 2:51 ` [PATCH 2/3] security: keys: Replace time_t with time64_t for struct key_preparsed_payload Baolin Wang
2017-08-09 2:51 ` [PATCH 3/3] net: rxrpc: Replace time_t type with time64_t type Baolin Wang
2017-08-09 9:01 ` Arnd Bergmann
2017-08-09 9:33 ` David Howells
2017-08-09 10:00 ` Arnd Bergmann
2017-08-09 13:26 ` David Howells
2017-08-09 15:12 ` Arnd Bergmann
2017-08-09 15:45 ` David Howells
2017-08-09 8:28 ` David Howells [this message]
2017-08-10 1:59 ` [PATCH 0/3] Fix y2038 issues for security/keys subsystem Baolin Wang
2017-08-21 12:12 ` Baolin Wang
2017-09-15 8:38 ` Baolin Wang
2017-08-09 8:44 ` Arnd Bergmann
2017-08-10 2:00 ` Baolin Wang
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=4455.1502267323@warthog.procyon.org.uk \
--to=dhowells@redhat$(echo .)com \
--cc=Jason@zx2c4$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=baolin.wang@linaro$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=dan.carpenter@oracle$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=james.l.morris@oracle$(echo .)com \
--cc=keyrings@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-security-module@vger$(echo .)kernel.org \
--cc=marc.dionne@auristor$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=serge@hallyn$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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