lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 26 Jun 2009 02:17:28 +0900 From: Paul Mundt <lethal@...ux-sh.org> To: "Rafael J. Wysocki" <rjw@...k.pl> Cc: Magnus Damm <magnus.damm@...il.com>, paul@...an.com, gregkh@...e.de, linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org Subject: Re: [linux-pm] [PATCH] Driver Core: Add platform device arch data V3 On Thu, Jun 25, 2009 at 04:34:11PM +0200, Rafael J. Wysocki wrote: > On Thursday 25 June 2009, Magnus Damm wrote: > > If possible, I'd like this to be merged as early as possible since a > > lot of processor specific changes will depend on it. With this > > included in 2.6.31 I can easily build arch specific code for 2.6.32. > > Anything I can do to make that happen? > > > > My top priority is Runtime PM for SuperH on top of your code, and I > > intend to post a prototype for SuperH before the PM Summit. It would > > be great to minimize the dependencies though, and including this in > > 2.6.31 would certainly help. > > I'm going to add this patch to my linux-next branch shortly and if your 2.6.32 > development is based on that branch (I'd recommend that anyway), there > shouldn't be any problems during the 2.6.32 merge window. > Yes, I was already planning on creating a topic branch based off of this so that we can start getting things ready in the sh tree, so this is not a problem.. as long as you don't rebase ;-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists