From: Xavier Bestel <xavier.bestel@free.fr>
To: Joachim Breuer <jmbreuer@gmx.net>
Cc: "Robert Love" <rml@tech9.net>, "Andrew Morton" <akpm@zip.com.au>,
"christophe barbé" <christophe.barbe.ml@online.fr>,
"Marcelo Tosatti" <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 3c59x and resume
Date: 25 Mar 2002 12:53:12 +0100 [thread overview]
Message-ID: <1017057192.22083.4.camel@bip> (raw)
In-Reply-To: <m3r8m851ad.fsf@venus.fo.et.local>
le lun 25-03-2002 à 12:34, Joachim Breuer a écrit :
> Being able to redetect a pulled card put in a different slot as a
> "known" one giving it the same eth<i> (and associated WOL etc. config)
> as before would of course be nice, but I can't see how this can be
> cleanly done over reboots.
Some may say that being able to give the same eth<i> to the same bus
position, even after swapping the card for a new one, is more important
- think of production machines which can't afford being off-service for
too long. You just shutdown, swap the cards, poweron and you go. No
reconfig, that's how it should run.
Xav
next prev parent reply other threads:[~2002-03-25 11:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-23 16:16 [PATCH] 3c59x and resume christophe barbé
2002-03-23 18:39 ` Andrew Morton
2002-03-23 20:06 ` Robert Love
2002-03-23 22:44 ` christophe barbé
2002-03-24 8:07 ` Greg KH
2002-03-24 14:25 ` christophe barbé
2002-03-25 18:01 ` Greg KH
2002-03-25 18:19 ` christophe barbé
2002-03-25 19:11 ` Greg KH
2002-03-25 20:27 ` christophe barbé
2002-03-25 20:58 ` christophe barbé
2002-03-25 11:34 ` Joachim Breuer
2002-03-25 11:53 ` Xavier Bestel [this message]
2002-03-25 21:31 ` Joachim Breuer
2002-03-25 19:44 ` Bill Davidsen
2002-03-25 20:16 ` christophe barbé
2002-03-26 0:57 ` Jeff Garzik
2002-03-26 1:40 ` christophe barbé
2002-03-26 4:10 ` Jeff Garzik
2002-03-26 4:39 ` christophe barbé
2002-03-26 4:50 ` Andrew Morton
2002-03-26 16:56 ` christophe barbé
2002-03-26 16:57 ` Jeff Garzik
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=1017057192.22083.4.camel@bip \
--to=xavier.bestel@free.fr \
--cc=akpm@zip.com.au \
--cc=christophe.barbe.ml@online.fr \
--cc=jmbreuer@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=rml@tech9.net \
/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