All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Andrey Savochkin <saw@saw.sw.com.sg>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>,
	Andrew Morton <akpm@zip.com.au>
Subject: Re: Fwd: eepro100 pm fix (fwd)
Date: Mon, 12 Nov 2001 21:36:12 -0500	[thread overview]
Message-ID: <20011112213612.A16461@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1005569101.17579.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.1005569101.17579.linux-kernel2news@redhat.com>; from saw@saw.sw.com.sg on Mon, Nov 12, 2001 at 03:50:03PM +0300

FYI:

The patch looks good but it does not help my case.
The eepro100 is dead after resume on my Sony PCG-Z505JE.
BTW, my difficulties started somewhere in 2.4.10 or thereabouts,
so they are probably unrelated to what Jens reported "a year ago".

-- Pete

> Path: post-office.corp.redhat.com!not-for-mail
> From: Andrey Savochkin <saw@saw.sw.com.sg>
> Newsgroups: linux-kernel
> Date: Mon, 12 Nov 2001 15:50:03 +0300
> Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>,
>    Andrew Morton <akpm@zip.com.au>
> To: torvalds@transmeta.com

> Linus,
> 
> Could you apply it, please?
> 
> 	Andrey
> 
> ----- Forwarded message from Jens Axboe <axboe@suse.de> -----
> 
> Date: Mon, 12 Nov 2001 13:24:53 +0100
> From: Jens Axboe <axboe@suse.de>
> To: saw@saw.sw.com.sg
> Subject: eepro100 pm fix
> Message-ID: <20011112132453.B786@suse.de>
> 
> Hi Andrey,
> 
> This patch posted by Andrew Morton makes the eepro100 actually survive a
> apm suspend and resume without totally croaking (a problem I reported
> probably a year or so ago :-). Any chance you could include it?
> 
> -- 
> Jens Axboe

           reply	other threads:[~2001-11-13  2:36 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <mailman.1005569101.17579.linux-kernel2news@redhat.com>]

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=20011112213612.A16461@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=akpm@zip.com.au \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.