From: Andy Tucker <agtucker@google.com>
To: avagin@gmail.com
Cc: ksummit-discuss@lists.linuxfoundation.org, dima@arista.com,
peterz@infradead.org, jdike@addtoit.com, oleg@redhat.com,
Victor Marmol <vmarmol@google.com>,
john.stultz@linaro.org, luto@kernel.org, gorcunov@openvz.org,
Adrian Reber <adrian@lisas.de>,
christian.brauner@ubuntu.com, xemul@virtuozzo.com
Subject: Re: [Ksummit-discuss] [TECH-TOPIC] Multiple time domains
Date: Sat, 3 Nov 2018 11:47:42 -0700 [thread overview]
Message-ID: <CAL+UND8UFOvan+oH2xQm1iXbyz-ahGUe5ta5GgqmyyN=MfkH-A@mail.gmail.com> (raw)
In-Reply-To: <20181103171320.GA20033@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
On Sat, Nov 3, 2018 at 10:13 AM Andrei Vagin <avagin@gmail.com> wrote:
> On Thu, Nov 01, 2018 at 02:21:26PM +0100, Thomas Gleixner wrote:
> > Sorry for the late proposal, but this popped up recently.
> >
> > The recent discussion of the proposed time name spaces resulted in a
> larger
> > range of questions how to handle that correctly. Aside of that we have
> > other requests of supporting multiple time domains for various reasons,
> > e.g. TSN folks in automotive and automation using grand clock masters
> with
> > a completely screwed time base.
> >
> > As most of the relevant developers seem to be at LPC, I propose a
> technical
> > session dedicated to discuss the handling of multiple time domains.
>
> I'm interested and going to be there.
>
> Cc: Andy and Victor
>
Thanks Andrei. I'm interested as well and will be at LPC for the full time.
[-- Attachment #2: Type: text/html, Size: 1195 bytes --]
next prev parent reply other threads:[~2018-11-03 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 13:21 [Ksummit-discuss] [TECH-TOPIC] Multiple time domains Thomas Gleixner
2018-11-01 17:33 ` Andy Lutomirski
2018-11-01 17:42 ` Eric W. Biederman
2018-11-01 20:09 ` Christian Brauner
2018-11-02 9:09 ` Pavel Emelianov
2018-11-03 17:13 ` Andrei Vagin
2018-11-03 18:47 ` Andy Tucker [this message]
2018-11-12 14:06 ` Dmitry Safonov
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='CAL+UND8UFOvan+oH2xQm1iXbyz-ahGUe5ta5GgqmyyN=MfkH-A@mail.gmail.com' \
--to=agtucker@google.com \
--cc=adrian@lisas.de \
--cc=avagin@gmail.com \
--cc=christian.brauner@ubuntu.com \
--cc=dima@arista.com \
--cc=gorcunov@openvz.org \
--cc=jdike@addtoit.com \
--cc=john.stultz@linaro.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=luto@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=vmarmol@google.com \
--cc=xemul@virtuozzo.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).