From: Andreas Roeseler <andreas.a.roeseler@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH V2] Add RFC 8335 Definitions from Linux 5.12
Date: Mon, 26 Apr 2021 11:16:41 -0500 [thread overview]
Message-ID: <e762d00b7e43ea8d17c203e125f964ba3b8d3fde.camel@gmail.com> (raw)
In-Reply-To: <874kftyqw2.fsf@oldenburg.str.redhat.com>
On Mon, 2021-04-26 at 18:03 +0200, Florian Weimer wrote:
> * Andreas Roeseler:
>
> > RFC 8335 defines the network utility PROBE, which builds off of the
> > capabilities of Ping to query more detailed interface information
> > from
> > networking nodes.
> >
> > The definitions included in this patchset have been accepted into
> > the
> > linux net-next branch and will be included in Linux 5.12. This
> > patchset adds the same definitions to the glibc for use in the
> > iputils package.
> >
> > The relevant commits for the Linux definitions can be found here:
> > https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=2b246b2569cd2ac6ff700d0dce56b8bae29b1842
> > https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=750f4fc2a12f6632b5aa04526bf57fa06bfe8467
>
> The names should be teh same on the glibc and Linus side. These
> commits
> still use the old names.
>
Ok then I think I misunderstood your comment on V1 of this patch.
Should I edit these definitions in Linux and then try to submit this
patch once they have been changed, or can the definitions in V1 of this
patch get merged?
> Thanks,
> Florian
>
next prev parent reply other threads:[~2021-04-26 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 16:01 Andreas Roeseler
2021-04-26 16:03 ` Florian Weimer
2021-04-26 16:16 ` Andreas Roeseler [this message]
2021-04-28 23:51 ` Andreas Roeseler
2021-04-30 9:56 ` Florian Weimer
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=e762d00b7e43ea8d17c203e125f964ba3b8d3fde.camel@gmail.com \
--to=andreas.a.roeseler@gmail.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).