ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Dealing with 2038
Date: Wed, 07 May 2014 10:28:35 -0700	[thread overview]
Message-ID: <536A6D43.6020300@linaro.org> (raw)
In-Reply-To: <20140507020743.GA6461@thunk.org>

On 05/06/2014 07:07 PM, Theodore Ts'o wrote:
> On Tue, May 06, 2014 at 03:06:27PM -0700, John Stultz wrote:
>> Right. So clearly I don't have all the details ready right this moment,
>> but I hope providing more detail above gives you a better sense of the
>> current proposals and some confidence that I'll try to do my homework
>> and have some discussions on lkml before the Kernel Summit discussion.
> Something else to consider is whether we would need to have some glibc
> folks present at the kernel summit if we want to discuss it there, and
> whether we should also think about also planning some discussions at
> the Plumber's Conference --- because there will certainly be userspace
> impacts that will need to be taken into account.

Do you have a sense of who might be a good glibc contact for this sort
of thing?

And yes, When I ran into Thomas at lsf-mm, we talked about splitting the
duty here, with me bringing it up at Kernel Summit as Thomas cannot
attend, and since I cannot attend Plumbers this year having Thomas
covering it there.

thanks
-john

  parent reply	other threads:[~2014-05-07 17:28 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 18:33 John Stultz
2014-05-05 19:23 ` Andy Lutomirski
2014-05-05 20:53 ` josh
2014-05-05 23:20   ` Andy Lutomirski
2014-05-06  2:12   ` H. Peter Anvin
2014-05-06  2:21     ` Josh Triplett
2014-05-06 12:57       ` Theodore Ts'o
2014-05-06 17:53         ` John Stultz
2014-05-06 18:20           ` Arnd Bergmann
2014-05-06 20:19             ` Theodore Ts'o
2014-05-06 20:33               ` josh
2014-05-06 20:50                 ` Theodore Ts'o
2014-05-06 22:06                   ` John Stultz
2014-05-07  2:07                     ` Theodore Ts'o
2014-05-07 11:19                       ` Jonathan Corbet
2014-05-07 17:28                       ` John Stultz [this message]
2014-05-09 15:05                         ` Theodore Ts'o
2014-05-08 20:37                       ` Ben Hutchings
2014-05-09 15:10                         ` Theodore Ts'o
2014-05-09 20:39                           ` Arnd Bergmann
2014-05-09 22:33                             ` Josh Triplett
2014-05-10  0:16                               ` H. Peter Anvin
2014-05-10  1:44                                 ` Rafael J. Wysocki
2014-05-15 12:18                                 ` Grant Likely
2014-05-15 17:20                                   ` H. Peter Anvin
2014-05-16  2:50                                     ` Jason Cooper
2014-05-10  0:19                               ` Andy Lutomirski
2014-05-06 21:17               ` Daniel Phillips
2014-05-06 21:56                 ` Luck, Tony
2014-05-07  1:56                   ` Daniel Phillips
2014-05-07 14:00         ` Grant Likely
2014-05-09 17:30       ` H. Peter Anvin
2014-05-06  1:25 ` Li Zefan

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=536A6D43.6020300@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=tytso@mit.edu \
    /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