linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yu, Luming" <luming.yu@intel.com>
To: "Pavel Machek" <pavel@ucw.cz>,
	"kernel list" <linux-kernel@vger.kernel.org>,
	"ACPI mailing list" <acpi-devel@lists.sourceforge.net>
Subject: RE: My current suspend bigdiff
Date: Thu, 4 Dec 2003 13:34:47 +0800	[thread overview]
Message-ID: <3ACA40606221794F80A5670F0AF15F8401720BFE@pdsmsx403.ccr.corp.intel.com> (raw)

>This is how my current "bigdiff" looks... [This is not for
>application, but if you want to make S3 working, it might help you].

I have some issues about entering S3. From device driver point of view,  
Could you please explain the main difference between entering S1 and S3.

             reply	other threads:[~2003-12-04  5:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04  5:34 Yu, Luming [this message]
2003-12-04 10:51 ` My current suspend bigdiff 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=3ACA40606221794F80A5670F0AF15F8401720BFE@pdsmsx403.ccr.corp.intel.com \
    --to=luming.yu@intel.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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;
as well as URLs for NNTP newsgroup(s).