linux-kernel - Re: Handling of suspend/hibernation patches

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200807032318.41446.rjw@sisk.pl>
Date:	Thu, 3 Jul 2008 23:18:40 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	stern@...land.harvard.edu, andi@...stfloor.org, greg@...ah.com,
	jbarnes@...tuousgeek.org, lenb@...nel.org,
	torvalds@...ux-foundation.org, linux-pm@...ts.linux-foundation.org,
	sfr@...b.auug.org.au, pavel@...e.cz, mingo@...e.hu
Subject: Re: Handling of suspend/hibernation patches

On Thursday, 3 of July 2008, Andrew Morton wrote:
> On Thu, 3 Jul 2008 22:47:32 +0200
> "Rafael J. Wysocki" <rjw@...k.pl> wrote:
> 
> > Hi,
> > 
> > Recently, we've had some problems with the handling of suspend/hibernation
> > patches, because they tend to touch multiple subsystems at a time.  As a
> > result, it usually is not clear which tree they should be included in and at
> > the moment there are suspend/hibernation patches in the PCI, ACPI, x86
> > trees, as well as in -mm.  Of course the resulting dependencies between those
> > trees are a pain to Stephen and their maintainers.
> > 
> > After the last Kernel Summit we tried to create a branch in the ACPI tree for
> > suspend/hibernation patches (thanks Len!) and that had worked quite well until
> > we started to work on the core device power management.  This coincided with
> > the creation of linux-next and collecting suspend/hibernation patches in the
> > ACPI tree became inconvenient.
> > 
> > Now, we could go back to the old way of handling suspend/hibernation patches,
> > which was to merge them through -mm, but the disadvantage of this would be that
> > the patches wouldn't go through linux-next.  However, I'd like
> > suspend/hibernation patches to be included in linux-next, so that they can get
> > as much testing as possible.
> 
> I need to get butt into gear and get most-of-mm into linux-next.  I'll
> be picking that up when 2.6.27-rc1 is done.
> 
> So we can just keep this tree in -mm (and hence linux-next) if you like.

Well, that will save me quite a bit patch management work. :-)

Let's keep that in -mm, then.

Thanks,
Rafael
--
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/