public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFC] Add support to resume swsusp from initrd
Date: Sun, 5 Dec 2004 22:49:49 +0100	[thread overview]
Message-ID: <20041205214949.GH1012@elf.ucw.cz> (raw)
In-Reply-To: <1102282928.9384.35.camel@tyrosine>

Hi!

> > > resume_device is set by swsusp_read, which requires name_to_dev_t to be
> > > working. At the point where that's called, the device driver hasn't been
> > > loaded and we don't have the information to get the dev_t. Once the
> > > driver has been loaded, name_to_dev_t has already been discarded (it's
> > > marked __init). So we need to set resume_device somehow.
> > 
> > What about move of resume_device setup somewhere sooner?
> 
> Ah - we could always set resume_device, even if there's nothing to
> resume. That way, it'd be set correctly for userspace later on. Ok, I
> think I can make that work.

Yes.

> > > Heh. Yes, that's no problem. A new bigdiff for -rc3 would be
> > > helpful.
> > 
> > Hmm, I'm still on 2.6.9, but this code did not change much. I'll
> > generate it.
> 
> Thanks!

It should be in the queue.
								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-12-05 21:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-05 20:48 [PATCH/RFC] Add support to resume swsusp from initrd Matthew Garrett
2004-12-05 21:12 ` Pavel Machek
2004-12-05 21:21   ` Matthew Garrett
2004-12-05 21:29     ` Pavel Machek
2004-12-05 21:42       ` Matthew Garrett
2004-12-05 21:49         ` Pavel Machek [this message]
2004-12-06 10:02   ` Stefan Seyfried
2004-12-05 21:18 ` Pavel Machek
2004-12-06 23:15   ` Matthew Garrett
2004-12-07  9:44     ` Pavel Machek
2004-12-07 11:39       ` Matthew Garrett
2004-12-07 11:46         ` Pavel Machek

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=20041205214949.GH1012@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox