netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: blueflux@koffein.net
Cc: kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com
Subject: Re: [PATCH] proc.txt document fix of error_burst and error_cost
Date: Thu, 09 Jan 2003 00:14:21 -0800 (PST)	[thread overview]
Message-ID: <20030109.001421.60144885.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0211071755470.5001-200000@laptop1.agatha>

   From: Oskar Andreasson <blueflux@koffein.net>
   Date: Thu, 7 Nov 2002 18:00:35 +0100 (CET)
   
   The patch should apply against both 2.4.19 and 2.5.45 without problems.
   
   Is there anything wrong with it, or may it be included? Suggestions? 

Patch applied, thanks.

      reply	other threads:[~2003-01-09  8:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-07 17:00 [PATCH] proc.txt document fix of error_burst and error_cost Oskar Andreasson
2003-01-09  8:14 ` David S. Miller [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=20030109.001421.60144885.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=blueflux@koffein.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@oss.sgi.com \
    /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;
as well as URLs for NNTP newsgroup(s).