From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
Andrew Morton <akpm@zip.com.au>
Subject: Re: dm: introduce pm_message_t
Date: Tue, 4 Jan 2005 14:10:20 +0100 [thread overview]
Message-ID: <20050104131020.GC3981@elf.ucw.cz> (raw)
In-Reply-To: <20050104130515.B18550@flint.arm.linux.org.uk>
Hi!
> > +FREEZE -- stop DMA and interrupts, and be prepared to reinit HW from
> > +scratch. That probably means stop accepting upstream requests, the
> > +actual policy of what to do with them beeing specific to a given
>
> busy busy bee. I think you mean "being".
Fixed locally, thanks. I guess I can fix this one with followup patch
if it indeed gets merged.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
prev parent reply other threads:[~2005-01-04 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 12:39 dm: introduce pm_message_t Pavel Machek
2005-01-04 13:05 ` Russell King
2005-01-04 13:10 ` Pavel Machek [this message]
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=20050104131020.GC3981@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.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