Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Diederik de Haas <didi.debian@cknow.org>
To:     Johannes Berg <johannes@sipsolutions.net>
Cc:     linux-wireless@vger.kernel.org,
        Diederik de Haas <didi.debian@cknow.org>
Subject: [PATCH] iw: fix 'upto' -> 'up to'
Date:   Sat, 23 Apr 2022 19:54:51 +0200
Message-Id: <20220423175451.27215-1-didi.debian@cknow.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

As reported by Debian's lintian tool.

Signed-off-by: Diederik de Haas <didi.debian@cknow.org>
---
In https://www.usingenglish.com/forum/threads/upto-or-up-to.137090/post-691624
a retired English teacher agrees: "Up to should always be two words."

 info.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/info.c b/info.c
index fa79ec7..ba33073 100644
--- a/info.c
+++ b/info.c
@@ -713,7 +713,7 @@ broken_combination:
 		rule = nla_data(tb_msg[NL80211_ATTR_COALESCE_RULE]);
 		pat = &rule->pat;
 		printf("\t\t * Maximum %u coalesce rules supported\n"
-		       "\t\t * Each rule contains upto %u patterns of %u-%u bytes,\n"
+		       "\t\t * Each rule contains up to %u patterns of %u-%u bytes,\n"
 		       "\t\t   maximum packet offset %u bytes\n"
 		       "\t\t * Maximum supported coalescing delay %u msecs\n",
 			rule->max_rules, pat->max_patterns, pat->min_pattern_len,
-- 
2.36.0