public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Michael Frank <mhf@linuxmail.org>
Subject: Re: swusp acpi
Date: Fri, 23 Jan 2004 07:08:25 +1300	[thread overview]
Message-ID: <1074794904.12773.72.camel@laptop-linux> (raw)
In-Reply-To: <20040122102655.GC200@elf.ucw.cz>

[-- Attachment #1: Type: text/plain, Size: 556 bytes --]

Hi.

Michael Frank has done a patch giving 2.4 PM support for serial ports
(my serial console now works flawlessly). Perhaps it could be ported to
2.6 and the driver model...

Nigel

On Thu, 2004-01-22 at 23:26, Pavel Machek wrote:
> Hi!
> 
> > > Not only serial console... Noone wrote serial port support.
> > 
> > Incorrect.  I never merged the changes because it's rather too hacky.
> 
> Who wrote them? Do you have that patch somewhere?
> 								Pavel
-- 
My work on Software Suspend is graciously brought to you by
LinuxFund.org.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-01-22 18:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21  9:43 swusp acpi tuija t.
2004-01-22  0:32 ` Pavel Machek
2004-01-22  1:45   ` Nigel Cunningham
2004-01-22 10:15     ` Pavel Machek
2004-01-22 10:22       ` Russell King
2004-01-22 10:26         ` Pavel Machek
2004-01-22 10:32           ` Russell King
2004-01-22 18:08           ` Nigel Cunningham [this message]
2004-01-22 20:43             ` Pavel Machek
2004-01-23  5:51             ` Michael Frank
     [not found] <BF1FE1855350A0479097B3A0D2A80EE0023E83B3@hdsmsx402.hd.intel.com>
2004-02-07  7:25 ` Len Brown
2004-02-07 11:50   ` Michael Frank

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=1074794904.12773.72.camel@laptop-linux \
    --to=ncunningham@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhf@linuxmail.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