From: Stephen Hemminger <stephen@networkplumber.org>
To: Maciek Machnikowski <maciejm@nvidia.com>
Cc: "marta.a.plantykow@intel.com" <marta.a.plantykow@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"people@netdevconf.info" <people@netdevconf.info>,
"milena.olech@intel.com" <milena.olech@intel.com>
Subject: Re: PTP-optimization code upstreamed
Date: Tue, 8 Feb 2022 12:47:54 -0800 [thread overview]
Message-ID: <20220208124754.02817343@hermes.local> (raw)
In-Reply-To: <BYAPR12MB2998E6F31AAAFBDF9294A092CC2D9@BYAPR12MB2998.namprd12.prod.outlook.com>
On Tue, 8 Feb 2022 19:43:13 +0000
Maciek Machnikowski <maciejm@nvidia.com> wrote:
> > -----Original Message-----
> > From: Stephen Hemminger <stephen@networkplumber.org>
> > Sent: Tuesday, February 8, 2022 6:55 PM
> > Subject: Re: PTP-optimization code upstreamed
> >
> > On Tue, 8 Feb 2022 14:23:41 +0100
> >
> > The process for contributing to upstream kernel is very well documented.
> > Links to github is useful, but does not start the upstream process.
> >
> > https://www.kernel.org/doc/html/latest/process/submitting-
> > patches.html#submittingpatches
> >
> > When can we expect patch set to show up on this mailing list?
>
> Hi Stephen,
>
> This code is not intended to be upstreamed, since it is a set of python scripts
> optimizing phc2sys and ptp4l servo.
> It reached the netdev mail list because it was presented on the NetDev
> conference, and some people were interested in them during the presentation.
>
> Have a great day!
> Maciek
Sure thanks. It still might be good to have this in tools directory.
Or somewhere related to kernel.
prev parent reply other threads:[~2022-02-08 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 13:23 PTP-optimization code upstreamed Marta Plantykow
2022-02-08 17:54 ` Stephen Hemminger
[not found] ` <MWHPR11MB177519F17F8BF5145DC773BBA82D9@MWHPR11MB1775.namprd11.prod.outlook.com>
2022-02-08 19:43 ` Maciek Machnikowski
2022-02-08 20:47 ` Stephen Hemminger [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=20220208124754.02817343@hermes.local \
--to=stephen@networkplumber.org \
--cc=maciejm@nvidia.com \
--cc=marta.a.plantykow@intel.com \
--cc=milena.olech@intel.com \
--cc=netdev@vger.kernel.org \
--cc=people@netdevconf.info \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.