[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170216184016.GI1968@nanopsycho>
Date: Thu, 16 Feb 2017 19:40:16 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, davem@...emloft.net, arkadis@...lanox.com,
idosch@...lanox.com, mlxsw@...lanox.com, jhs@...atatu.com,
ivecera@...hat.com, roopa@...ulusnetworks.com,
f.fainelli@...il.com, vivien.didelot@...oirfairelinux.com,
john.fastabend@...il.com
Subject: Re: [patch net-next RFC 0/8] Add support for pipeline debug (dpipe)
Thu, Feb 16, 2017 at 06:04:46PM CET, andrew@...n.ch wrote:
>On Thu, Feb 16, 2017 at 04:22:36PM +0100, Jiri Pirko wrote:
>> From: Jiri Pirko <jiri@...lanox.com>
>
>Hi Jiri, Arkadi
>
>Just to make sure we are all on the same page here:
>
>This purely RFC. It is not intended for the merge window starting next
>week?
No. We are aiming next net-next open.
>
>This is a new binary API, something we have to live with forever. So i
>think before it gets merged into a Linus kernel, we need time to think
>about all the different sorts of tables we want to dump, what sort of
>fields they have, and can we represent them using this API. That is
>going to take some time.
Agreed.
Powered by blists - more mailing lists