From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932526AbbB0Wkh (ORCPT <rfc822;w@1wt.eu>);
	Fri, 27 Feb 2015 17:40:37 -0500
Received: from v094114.home.net.pl ([79.96.170.134]:64096 "HELO
	v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with SMTP id S932505AbbB0Wkg (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 27 Feb 2015 17:40:36 -0500
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Mark Rutland <mark.rutland@arm.com>, linux-kernel@vger.kernel.org,
        linux-arm-kernel@lists.infradead.org,
        Boris Brezillon <boris.brezillon@free-electrons.com>,
        Ian Campbell <ian.campbell@citrix.com>,
        Peter Zijlstra <peterz@infradead.org>,
        "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
        Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] genirq: better describe IRQF_NO_SUSPEND semantics
Date: Sat, 28 Feb 2015 00:04:04 +0100
Message-ID: <1861422.rtsUbbsKiF@vostro.rjw.lan>
User-Agent: KMail/4.11.5 (Linux/3.19.0+; KDE/4.11.5; x86_64; ; )
In-Reply-To: <20150227152313.7247ed2c@lwn.net>
References: <1424444026-31231-1-git-send-email-mark.rutland@arm.com> <1425092792.1YLq228Omk@vostro.rjw.lan> <20150227152313.7247ed2c@lwn.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="utf-8"
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Friday, February 27, 2015 03:23:13 PM Jonathan Corbet wrote:
> On Fri, 27 Feb 2015 23:41:05 +0100
> "Rafael J. Wysocki" <rjw@rjwysocki.net> wrote:
> 
> > > Applied (with Peter's ack) to the docs tree.  
> > 
> > Well, I've applied it too in the meantime. :-)
> > 
> > Also I'll have more commits on top of it, so it's better if it goes through
> > my tree I think, if you don't mind.
> 
> Gee, I feel like I've been here before :)
> 
> In the future, would you like me to avoid taking patches to
> Documentation/power?

Well, I tend to apply them as a rule, unless I overlook them.  That usually
happens if they aren't CCed to me directly or to linux-pm.

But yeah, you can safely avoid patches touching Documentation/power/ or
Documentation/acpi/, I'll be taking care of them.

> I'll drop it out of my tree.

Thanks!


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.