From: David Howells <dhowells@redhat•com>
To: Arnd Bergmann <arnd@arndb•de>
Cc: dhowells@redhat•com, Baolin Wang <baolin.wang@linaro•org>,
David Miller <davem@davemloft•net>,
james.l.morris@oracle•com, "Serge E. Hallyn" <serge@hallyn•com>,
marc.dionne@auristor•com,
Dan Carpenter <dan.carpenter@oracle•com>,
"Jason A. Donenfeld" <Jason@zx2c4•com>,
Mark Brown <broonie@kernel•org>,
keyrings@vger•kernel.org,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
LSM List <linux-security-module@vger•kernel.org>,
Networking <netdev@vger•kernel.org>
Subject: Re: [PATCH 3/3] net: rxrpc: Replace time_t type with time64_t type
Date: Wed, 09 Aug 2017 14:26:45 +0100 [thread overview]
Message-ID: <11686.1502285205@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAK8P3a3L11rXAV8-hE1fNtAZyMBNnQneRm5g7F8VDmk7HjQV4A@mail.gmail.com>
Arnd Bergmann <arnd@arndb•de> wrote:
> Do you know which format is used in practice? Are both kad and k5 common
> among rxrpc users?
The aklog program I'm using uses the non-XDR interface to push a Kerberos 5
ticket to the kernel, so it doesn't actually invoke rxrpc_preparse_xdr() from
rxrpc_preparse().
David
next prev parent reply other threads:[~2017-08-09 13:26 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 [this message]
2017-08-09 15:12 ` Arnd Bergmann
2017-08-09 15:45 ` David Howells
2017-08-09 8:28 ` [PATCH 0/3] Fix y2038 issues for security/keys subsystem David Howells
2017-08-10 1:59 ` 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=11686.1502285205@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