From: John Stultz <john.stultz@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "Amit Pundir" <amit.pundir@linaro.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
"Android Kernel Team" <kernel-team@android.com>
Subject: Re: [PATCH v3] epoll: drop EPOLLWAKEUP if PM_SLEEP is disabled
Date: Fri, 15 Nov 2013 14:35:16 -0800 [thread overview]
Message-ID: <5286A1A4.2020905@linaro.org> (raw)
In-Reply-To: <2338693.sZIlYGM98f@vostro.rjw.lan>
On 11/15/2013 02:40 PM, Rafael J. Wysocki wrote:
> On Friday, November 15, 2013 10:53:01 AM John Stultz wrote:
>> On 11/15/2013 07:10 AM, Rafael J. Wysocki wrote:
>>> On Friday, November 15, 2013 12:56:31 PM Amit Pundir wrote:
>>>> Drop EPOLLWAKEUP from epoll events mask if CONFIG_PM_SLEEP is disabled.
>>>>
>>>> Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
>>> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>>>
>>> Or am I supposed to take care of this?
>> I would assume it would be you, but maybe Al would prefer to take it?
>>
>> Also, should this be also marked for stable?
> Well, do people see it in production?
I guess its unlikely, but it seems like its possible. I guess I've got
no objection to holding off unless someone else hits this.
thanks
-john
next prev parent reply other threads:[~2013-11-15 22:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 7:26 [PATCH v3] epoll: drop EPOLLWAKEUP if PM_SLEEP is disabled Amit Pundir
2013-11-15 15:10 ` Rafael J. Wysocki
2013-11-15 18:53 ` John Stultz
2013-11-15 22:40 ` Rafael J. Wysocki
2013-11-15 22:35 ` John Stultz [this message]
2013-11-15 23:53 ` Rafael J. Wysocki
2013-11-25 19:38 ` John Stultz
2013-11-25 21:06 ` Rafael J. Wysocki
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=5286A1A4.2020905@linaro.org \
--to=john.stultz@linaro.org \
--cc=amit.pundir@linaro.org \
--cc=arve@android.com \
--cc=kernel-team@android.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viro@zeniv.linux.org.uk \
/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).