All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Patrick Mochel <mochel@digitalimplant.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Andrew Morton <akpm@osdl.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Status with pmdisk/swsusp merge ?
Date: Sun, 8 Aug 2004 20:22:34 +0200	[thread overview]
Message-ID: <20040808182234.GA620@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.50.0408051517141.6736-100000@monsoon.he.net>

Hi!

> > What is the status with those patches ?
> >
> > I have some additional stuff to drop on top of it, including the basic
> > PPC support, some renumbering of the states as discussed earlier, some
> > driver fixes etc.... but at this point, I feel it would be more handy
> > to get those in only after Patrick core changes have been merged with
> > Linus. Do we wait for 2.6.9 to open ?
> 
> I intend to try and merge my tree with Linus once he releases 2.6.8,
> modulo any bugs that crop up between now and then. Feel free to send me
> the patches to fix up ppc before then, and I will merge them as well.

Sounds good.

> As far as the device power management stuff goes, I'm wading through the
> discussion right now..

Hopefully we can at least switch to enums so that we clear any
confusion....
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

  reply	other threads:[~2004-08-08 18:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05  4:18 Status with pmdisk/swsusp merge ? Benjamin Herrenschmidt
2004-08-05 10:27 ` Nigel Cunningham
2004-08-05 22:21 ` Patrick Mochel
2004-08-08 18:22   ` Pavel Machek [this message]
2004-08-09 15:35     ` Disconnect
2004-08-12 21:04       ` Pavel Machek
2004-08-12 21:13         ` Alan Cox
2004-08-12 23:01         ` Olivier Galibert

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=20040808182234.GA620@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@digitalimplant.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.