From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Kroah-Hartman Subject: Re: [PATCH 3.10.y+] PM / sleep: Use valid_state() for platform-dependent sleep states only Date: Fri, 5 Sep 2014 14:47:58 -0700 Message-ID: <20140905214758.GC30221@kroah.com> References: <1849024.CHOUso6H2K@vostro.rjw.lan> <1409865665-5375-1-git-send-email-computersforpeace@gmail.com> <54095835.7000207@gmail.com> <20140905074512.GA12218@brian-ubuntu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20140905074512.GA12218@brian-ubuntu> Sender: stable-owner@vger.kernel.org To: Brian Norris Cc: Francis Moreau , stable@vger.kernel.org, linux-pm@vger.kernel.org, Linux Kernel , "Rafael J. Wysocki" List-Id: linux-pm@vger.kernel.org On Fri, Sep 05, 2014 at 12:45:12AM -0700, Brian Norris wrote: > On Fri, Sep 05, 2014 at 08:29:09AM +0200, Francis Moreau wrote: > > On 09/04/2014 11:21 PM, Brian Norris wrote: > [...] > > > Signed-off-by: Rafael J. Wysocki > > > Cc: # 3.10+: 27ddcc6596e5: PM / sleep: Add state field to pm_states[] entries > > > Cc: # 3.10+ > > > --- > > > This is a backport request for these two commits upstream: > > > > > > 27ddcc6596e5 PM / sleep: Add state field to pm_states[] entries > > > 43e8317b0bba PM / sleep: Use valid_state() for platform-dependent sleep states only > > > > > > > Wouldn't it be cleaner to have 2 separate backports then ? > > The first is purely a dependency for the second. It has no value on its > own. So I thought the above form made sense and followed the process > mentioned in Documentation/stable_kernel_rules.txt. > > Admittedly, it's a little asymmetric. But I really don't know what the > "best" option is, since I'd prefer not having to send around any patch > text at all, unless the backport is not trivial (these apply cleanly). If they apply cleanly, then just list the git commit ids, and I can take care of the rest. Don't merge patches together, it just causes problems and makes it harder to track what is going on. thanks, greg k-h