All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: LKML <linux-kernel@vger.kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	Andi Kleen <andi@firstfloor.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Greg KH <greg@kroah.com>, Jesse Barnes <jbarnes@virtuousgeek.org>,
	Len Brown <lenb@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	pm list <linux-pm@lists.linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Pavel Machek <pavel@suse.cz>, Ingo Molnar <mingo@elte.hu>
Subject: Handling of suspend/hibernation patches
Date: Thu, 3 Jul 2008 22:47:32 +0200	[thread overview]
Message-ID: <200807032247.34049.rjw@sisk.pl> (raw)

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.

For this reason I'd like to create a quilt-based series of suspend/hibernation
(PM sleep) patches, that Stephen will be able to pull from, with the following
rules:
* the patch series will be based on linux-next and will be rebased as often
  as necessary
* the patch series will be periodically (most probably once a week) posted
  to linux-pm and linux-acpi; additionally the maintainers of the subsystems
  affected by the patches will be sent CCs of the messages with them, so that
  they can pick those patches up
* patches taken into the other subsystem trees will be dropped from the
  patchset and the resulting dependencies will be reflected by the annotations
  in the 'series' file
* the patches that are still in the series when the merge window opens, but
  are accepted by the appropriate maintainers, will be put into a git branch
  and pushed to Linus towards the end of the merge window.

If you agree to this plan, I'd like to start by creating the patch series out
of the suspend/hibernation patches that are in -mm at the moment and one
additional patch that was accepted by Len, but not added to the ACPI tree
because of some dependencies with the other subsystem trees.

Thanks,
Rafael


-- 
"Premature optimization is the root of all evil." - Donald Knuth

             reply	other threads:[~2008-07-03 20:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 20:47 Rafael J. Wysocki [this message]
2008-07-03 21:01 ` Handling of suspend/hibernation patches Andrew Morton
2008-07-03 21:18   ` Rafael J. Wysocki
2008-07-03 21:18   ` Rafael J. Wysocki
2008-07-03 21:01 ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2008-07-03 20:47 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=200807032247.34049.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=greg@kroah.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mingo@elte.hu \
    --cc=pavel@suse.cz \
    --cc=sfr@canb.auug.org.au \
    --cc=stern@rowland.harvard.edu \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.