linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alberto Bertogli <albertogli@telpin.com.ar>
To: netdev@oss.sgi.com
Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] IPVS' Kconfig LBLC and LBLCR configuration typo
Date: Mon, 14 Jul 2003 11:03:50 -0300	[thread overview]
Message-ID: <20030714140350.GB1389@telpin.com.ar> (raw)


Hi there!

The following patch fixes what looks like a typo in ipvs' Kconfig
(net/ipv4/ipvs/Kconfig).

Both the IP_VS_LBLC and IP_VS_LBLCR schedulings have the same tristate
line (well, not the same, IP_VS_LBLCR's has a 'g' missing at the end):

tristate "locality-based least-connection with replication scheduling"

But it looks like LBLC should be "locality-based least-connection
scheduling" and LBLCR "locality-based least-connection with replication
scheduling".


Thanks,
		Alberto


--- Kconfig.orig	2003-07-14 10:32:06.000000000 -0300
+++ Kconfig	2003-07-14 10:32:57.000000000 -0300
@@ -147,7 +147,7 @@
 	  unsure, say N.
 
 config	IP_VS_LBLC
-	tristate "locality-based least-connection with replication scheduling"
+	tristate "locality-based least-connection scheduling"
         depends on IP_VS
 	---help---
 	  The locality-based least-connection scheduling algorithm is for
@@ -163,7 +163,7 @@
 	  unsure, say N.
 
 config  IP_VS_LBLCR
-	tristate "locality-based least-connection with replication schedulin"
+	tristate "locality-based least-connection with replication scheduling"
         depends on IP_VS
 	---help---
 	  The locality-based least-connection with replication scheduling




             reply	other threads:[~2003-07-14 13:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 14:03 Alberto Bertogli [this message]
2003-07-14 20:16 ` [PATCH] IPVS' Kconfig LBLC and LBLCR configuration typo Roberto Nibali

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=20030714140350.GB1389@telpin.com.ar \
    --to=albertogli@telpin.com.ar \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --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).