From: Jakub Kicinski <kuba@kernel.org>
To: David Yang <mmyangfl@gmail.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Shuah Khan <shuah@kernel.org>, Ido Schimmel <idosch@nvidia.com>,
Yong Wang <yongwang@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Petr Machata <petrm@nvidia.com>, Andy Roulin <aroulin@nvidia.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Amit Cohen <amcohen@nvidia.com>,
Alessandro Zanni <alessandro.zanni87@gmail.com>,
Li Shuang <shuali@redhat.com>, Xin Long <lucien.xin@gmail.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: forwarding: Reorder arguments to obey POSIX getopt
Date: Fri, 5 Sep 2025 17:57:16 -0700 [thread overview]
Message-ID: <20250905175716.098114bd@kernel.org> (raw)
In-Reply-To: <20250905173947.3164807-1-mmyangfl@gmail.com>
On Sat, 6 Sep 2025 01:39:41 +0800 David Yang wrote:
> Quoted from musl wiki:
>
> GNU getopt permutes argv to pull options to the front, ahead of
> non-option arguments. musl and the POSIX standard getopt stop
> processing options at the first non-option argument with no
> permutation.
>
> Thus these scripts stop working on musl since non-option arguments do
> not always come last. Fix it by reordering arguments.
Have you tested this? You seem to be breaking mausezahn.
--
pw-bot: cr
prev parent reply other threads:[~2025-09-06 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 17:39 [PATCH net-next] selftests: forwarding: Reorder arguments to obey POSIX getopt David Yang
2025-09-06 0:57 ` Jakub Kicinski [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=20250905175716.098114bd@kernel.org \
--to=kuba@kernel.org \
--cc=alessandro.zanni87@gmail.com \
--cc=amcohen@nvidia.com \
--cc=aroulin@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=mmyangfl@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=shuah@kernel.org \
--cc=shuali@redhat.com \
--cc=vladimir.oltean@nxp.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yongwang@nvidia.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).