From: Jeff Garzik <jgarzik@pobox•com>
To: Stefan Rompf <srompf@isg•de>
Cc: davem@redhat•com, netdev@oss•sgi.com
Subject: Re: Patch: Backport of link state notification to 2.4.20
Date: Tue, 03 Dec 2002 19:45:27 -0500 [thread overview]
Message-ID: <3DED5027.7070807@pobox.com> (raw)
In-Reply-To: <3DED4FB4.5070700@pobox.com>
Jeff Garzik wrote:
> Stefan Rompf wrote:
>
>> Hi David,
>>
>> attached is the recent backport of link state notification for the
>> stable kernel series. The feature is optional and can be configured away
>> to nothing, and tested on several systems.
>>
>
> It might be a backport, but I haven't seen a 2.5.x version posted in a
> while. If this is going into the stable series, it should already be
> merged in 2.5.x at the same time, if not first.
...and of course this email arrives immediately in my inbox ;-)
Which leads to the question: why CONFIG_LINKWATCH in 2.4 but not 2.5?
Let's do the same in both kernels unless there is a good reason not to...
prev parent reply other threads:[~2002-12-04 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 22:28 Patch: Backport of link state notification to 2.4.20rc1 Stefan Rompf
2002-11-14 11:43 ` bert hubert
2002-11-15 13:20 ` Stefan Rompf
2002-12-03 22:28 ` Patch: Backport of link state notification to 2.4.20 Stefan Rompf
2002-12-04 0:43 ` Jeff Garzik
2002-12-04 0:45 ` Jeff Garzik [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=3DED5027.7070807@pobox.com \
--to=jgarzik@pobox$(echo .)com \
--cc=davem@redhat$(echo .)com \
--cc=netdev@oss$(echo .)sgi.com \
--cc=srompf@isg$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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