From: Pavel Emelyanov <xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
To: Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Peter Zijlstra <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: Michael Kerrisk
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Matthew Helsley
<matt.helsley-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 0/3] posix timers: Extend kernel API to report more info about timers (v3)
Date: Thu, 11 Apr 2013 15:56:27 +0400 [thread overview]
Message-ID: <5166A4EB.3000909@parallels.com> (raw)
In-Reply-To: <515051ED.7060306-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
On 03/25/2013 05:32 PM, Pavel Emelyanov wrote:
> On 03/11/2013 01:11 PM, Pavel Emelyanov wrote:
>> Hi.
>>
>> This v3 series is ported on v3.9-rc2 and patches' changelogs are fixed
>> according to Thomas' feedback to contain info why the change is required.
>
> Gentlemen,
>
> I'm sorry for bothering you again, but I've (hopefully) addressed the issues
> Thomas pointed out with the previous version of this set, thus I would like
> to ask you about your plans about it. If there's anything else I should do,
> just let me know.
Dear Sirs,
Any feedback on this set will be highly appreciated.
Yours sincerely,
Pavel
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Emelyanov <xemul@parallels.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
Matthew Helsley <matt.helsley@gmail.com>,
linux-api@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] posix timers: Extend kernel API to report more info about timers (v3)
Date: Thu, 11 Apr 2013 15:56:27 +0400 [thread overview]
Message-ID: <5166A4EB.3000909@parallels.com> (raw)
In-Reply-To: <515051ED.7060306@parallels.com>
On 03/25/2013 05:32 PM, Pavel Emelyanov wrote:
> On 03/11/2013 01:11 PM, Pavel Emelyanov wrote:
>> Hi.
>>
>> This v3 series is ported on v3.9-rc2 and patches' changelogs are fixed
>> according to Thomas' feedback to contain info why the change is required.
>
> Gentlemen,
>
> I'm sorry for bothering you again, but I've (hopefully) addressed the issues
> Thomas pointed out with the previous version of this set, thus I would like
> to ask you about your plans about it. If there's anything else I should do,
> just let me know.
Dear Sirs,
Any feedback on this set will be highly appreciated.
Yours sincerely,
Pavel
next prev parent reply other threads:[~2013-04-11 11:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 9:11 [PATCH 0/3] posix timers: Extend kernel API to report more info about timers (v3) Pavel Emelyanov
2013-03-11 9:11 ` Pavel Emelyanov
[not found] ` <513D9FD9.6020507-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-03-11 9:12 ` [PATCH 1/3] posix timers: Allocate timer id per process (v2) Pavel Emelyanov
2013-03-11 9:12 ` Pavel Emelyanov
2013-04-17 19:53 ` [tip:timers/core] posix timers: Allocate timer id per process (v2 ) tip-bot for Pavel Emelyanov
2013-03-11 9:12 ` [PATCH 2/3] posix-timers: Introduce /proc/<pid>/timers file Pavel Emelyanov
2013-03-11 9:12 ` Pavel Emelyanov
2013-04-17 19:54 ` [tip:timers/core] posix-timers: Introduce /proc/PID/timers file tip-bot for Pavel Emelyanov
2013-03-11 9:13 ` [PATCH 3/3] posix-timers: Show sigevent info in proc file Pavel Emelyanov
2013-03-11 9:13 ` Pavel Emelyanov
2013-04-17 19:56 ` [tip:timers/core] " tip-bot for Pavel Emelyanov
2013-03-25 13:32 ` [PATCH 0/3] posix timers: Extend kernel API to report more info about timers (v3) Pavel Emelyanov
[not found] ` <515051ED.7060306-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-04-11 11:56 ` Pavel Emelyanov [this message]
2013-04-11 11:56 ` Pavel Emelyanov
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=5166A4EB.3000909@parallels.com \
--to=xemul-bzqdu9zft3wakbo8gow8eq@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt.helsley-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.