From: Greg KH <greg@kroah.com>
To: "Gross, Mark" <mark.gross@intel.com>
Cc: David Brownell <david-b@pacbell.net>,
Linus Torvalds <torvalds@osdl.org>,
linux-pm@lists.osdl.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH 2/2] Fix console handling duringsuspend/resume
Date: Thu, 29 Jun 2006 15:59:46 -0700 [thread overview]
Message-ID: <20060629225946.GC26175@kroah.com> (raw)
In-Reply-To: <5389061B65D50446B1783B97DFDB392D019DE2D5@orsmsx411.amr.corp.intel.com>
On Thu, Jun 29, 2006 at 01:13:03PM -0700, Gross, Mark wrote:
> >AS FAR AS I CAN TELL the patch won't actually change any behaviour (I
> have
> >actually been running for the last few days with the separate patch
> that
> >_does_ do that - moves the PCI config suspend/resume to the late/early
> >rsume phase), but hey, mistakes happen.
> >
>
> Shouldn't this type of thing go through the MM-tree first for these
> reasons?
Good point, that's probably the correct way to do this for such a core
change.
thanks,
greg k-h
next prev parent reply other threads:[~2006-06-29 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 20:13 [PATCH 2/2] Fix console handling duringsuspend/resume Gross, Mark
2006-06-29 22:59 ` Greg KH [this message]
2006-06-30 4:01 ` David Brownell
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=20060629225946.GC26175@kroah.com \
--to=greg@kroah.com \
--cc=david-b@pacbell.net \
--cc=linux-pm@lists.osdl.org \
--cc=mark.gross@intel.com \
--cc=pavel@ucw.cz \
--cc=torvalds@osdl.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