From: Andrew Morton <akpm@linux-foundation.org>
To: mtk.manpages@gmail.com
Cc: Andrei Vagin <avagin@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linux API <linux-api@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
"Eric W . Biederman" <ebiederm@xmission.com>,
Dmitry Safonov <0x7f454c46@gmail.com>
Subject: Re: [PATCH v2] timens: show clock symbolic names in /proc/pid/timens_offsets
Date: Mon, 13 Apr 2020 15:47:46 -0700 [thread overview]
Message-ID: <20200413154746.39275d0981f69e57a7ecab3e@linux-foundation.org> (raw)
In-Reply-To: <CAKgNAki6uBHVTBdJvj7hzbho9Z94MWRV7ab8npduogQohRndBQ@mail.gmail.com>
On Sun, 12 Apr 2020 07:51:47 +0200 "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com> wrote:
> Hi Andrei,
>
> On Sat, 11 Apr 2020 at 17:40, Andrei Vagin <avagin@gmail.com> wrote:
> >
> > Michael Kerrisk suggested to replace numeric clock IDs on symbolic
> > names.
> >
> > Now the content of these files looks like this:
> > $ cat /proc/774/timens_offsets
> > monotonic 864000 0
> > boottime 1728000 0
>
> Thanks.
>
> Assuming no-one has objections to the patch, please do mark for stable@.
>
`grep -r timens_offsets Documentation' comes up blank. Is
/proc/pid/timens_offsets documented anywhere? If not, it should be!
And this patch should update that documentation.
I assume the time namespace feature itself is documented under clone(2)?
next prev parent reply other threads:[~2020-04-13 22:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 6:52 [PATCH] timens: show clock symbolic names in /proc/pid/timens_offsets Andrei Vagin
2020-04-11 10:32 ` Michael Kerrisk (man-pages)
2020-04-11 10:36 ` Michael Kerrisk (man-pages)
2020-04-11 15:40 ` [PATCH v2] " Andrei Vagin
2020-04-12 5:51 ` Michael Kerrisk (man-pages)
2020-04-13 22:47 ` Andrew Morton [this message]
2020-04-14 0:04 ` Andrei Vagin
2020-04-14 9:51 ` Michael Kerrisk (man-pages)
2020-04-16 6:56 ` Andrei Vagin
2020-04-16 7:10 ` Michael Kerrisk (man-pages)
2020-04-16 9:52 ` Thomas Gleixner
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=20200413154746.39275d0981f69e57a7ecab3e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=0x7f454c46@gmail.com \
--cc=avagin@gmail.com \
--cc=ebiederm@xmission.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=tglx@linutronix.de \
/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).