From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: David Marchand <david.marchand@redhat.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "dts@dpdk.org" <dts@dpdk.org>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"Lijuan Tu" <lijuan.tu@intel.com>,
"Owen Hilyard" <ohilyard@iol.unh.edu>, nd <nd@arm.com>,
nd <nd@arm.com>
Subject: RE: TODO - remove dependency on ifconfig
Date: Wed, 11 Jan 2023 14:46:43 +0000 [thread overview]
Message-ID: <DBAPR08MB58141A2DD2C9299F15A4C33B98FC9@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8xoZ4CFRCE3ArdT5hLTQZMUPPWSM+bMARXWNx1jWfAwoA@mail.gmail.com>
<snip>
>
> On Tue, Jan 10, 2023 at 9:19 PM Stephen Hemminger
> <stephen@networkplumber.org> wrote:
> >
> > It would be good if DTS and DPDK docs and test did not use the ifconfig
> command.
> > Ifconfig is not maintained and is deprecated. Some distros have stopped
> shipping it.
> > Ifconfig only used ioctl's and was never updated to handle the many
> > kinds of interfaces and devices in Linux.
> >
> > The documentation part is relatively straight forward, but there are
> > lots
>
> Can you send patches for the doc?
>
> > of calls to ifconfig in DTS.
>
> Cc: dts@ and people involved in dts cleaning up
We discussed this topic, the DTS patch that was merged in the last DPDK release does not need ifconfig. The future patches, for dpdk repo, will use 'ip' command.
The existing DTS tree will not be changed.
>
>
> --
> David Marchand
prev parent reply other threads:[~2023-01-11 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230110121933.2e0989fa@hermes.local>
2023-01-11 7:40 ` David Marchand
2023-01-11 14:46 ` Honnappa Nagarahalli [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=DBAPR08MB58141A2DD2C9299F15A4C33B98FC9@DBAPR08MB5814.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dts@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=lijuan.tu@intel.com \
--cc=nd@arm.com \
--cc=ohilyard@iol.unh.edu \
--cc=stephen@networkplumber.org \
/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).