From: "Ariel Otilibili-Anieli" <Ariel.Otilibili-Anieli@eurecom.fr>
To: wireguard@lists.zx2c4.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>
Subject: [PATCH] wireguard-tools: Extracted error message for the sake of legibility
Date: Mon, 18 Nov 2024 23:58:18 +0100 [thread overview]
Message-ID: <15e782-673bc680-4ed-422b5480@29006332> (raw)
Hello,
This is a reminder about a patch sent to the WireGuard mailing list; CCing the maintainers of drivers/net/wireguard/; below a verbatim of my cover letter.
Thank you,
**
I have been using WireGuard for some time; it does ease the configuration of
VPNs. This is my first patch to the list, I asked to be subscribed; please
confirm me it is the case.
I would like to improve my C programming skills; your feedback will be much
appreciated.
Ariel
-------- Original Message --------
Subject: [PATCH] wireguard-tools: Extracted error message for the sake of legibility
Date: Thursday, August 01, 2024 11:43 CEST
From: Ariel Otilibili <Ariel.Otilibili-Anieli@eurecom.fr>
Reply-To: Ariel Otilibili <Ariel.Otilibili-Anieli@eurecom.fr>
To: wireguard@lists.zx2c4.com
CC: "Jason A . Donenfeld" <Jason@zx2c4.com>, Ariel Otilibili <Ariel.Otilibili-Anieli@eurecom.fr>
References: <20240725204917.192647-2-otilibil@eurecom.fr> <20240801094932.4502-1-otilibil@eurecom.fr>
Signed-off-by: Ariel Otilibili <otilibil@eurecom.fr>
---
src/set.c | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/src/set.c b/src/set.c
index 75560fd..b2fbd54 100644
--- a/src/set.c
+++ b/src/set.c
@@ -16,9 +16,19 @@ int set_main(int argc, const char *argv[])
{
struct wgdevice *device = NULL;
int ret = 1;
+ const char *error_message = "Usage: %s %s <interface>"
+ " [listen-port <port>]"
+ " [fwmark <mark>]"
+ " [private-key <file path>]"
+ " [peer <base64 public key> [remove]"
+ " [preshared-key <file path>]"
+ " [endpoint <ip>:<port>]"
+ " [persistent-keepalive <interval seconds>]"
+ " [allowed-ips <ip1>/<cidr1>[,<ip2>/<cidr2>]...]"
+ " ]...\n";
if (argc < 3) {
- fprintf(stderr, "Usage: %s %s <interface> [listen-port <port>] [fwmark <mark>] [private-key <file path>] [peer <base64 public key> [remove] [preshared-key <file path>] [endpoint <ip>:<port>] [persistent-keepalive <interval seconds>] [allowed-ips <ip1>/<cidr1>[,<ip2>/<cidr2>]...] ]...\n", PROG_NAME, argv[0]);
+ fprintf(stderr, error_message, PROG_NAME, argv[0]);
return 1;
}
--
2.45.2
next reply other threads:[~2024-11-19 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 22:58 Ariel Otilibili-Anieli [this message]
[not found] <20240801093257.2700-2-otilibil@eurecom.fr>
2024-08-01 9:32 ` Ariel Otilibili
-- strict thread matches above, loose matches on Subject: below --
2024-07-25 20:42 Ariel Otilibili
[not found] ` <20240801094932.4502-1-otilibil@eurecom.fr>
2024-08-01 9:43 ` [PATCH] wireguard-tools: " Ariel Otilibili
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=15e782-673bc680-4ed-422b5480@29006332 \
--to=ariel.otilibili-anieli@eurecom.fr \
--cc=Jason@zx2c4.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wireguard@lists.zx2c4.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).