[RFC PATCH 2/7] telemetry: add uint type as alias for u64

2022-12-13 Thread Bruce Richardson
For future standardization on the "uint" name for unsigned values rather than the existing "u64" one, we can for now: * rename all internal values to use uint rather than u64 * add new function names to alias the existing u64 ones Suggested-by: Morten Brørup Signed-off-by: Bruce Richardson ---

Re: [RFC PATCH 2/7] telemetry: add uint type as alias for u64

2022-12-14 Thread Tyler Retzlaff
On Tue, Dec 13, 2022 at 06:27:25PM +, Bruce Richardson wrote: > For future standardization on the "uint" name for unsigned values rather > than the existing "u64" one, we can for now: > * rename all internal values to use uint rather than u64 > * add new function names to alias the existing u64

Re: [RFC PATCH 2/7] telemetry: add uint type as alias for u64

2022-12-14 Thread lihuisong (C)
在 2022/12/14 2:27, Bruce Richardson 写道: For future standardization on the "uint" name for unsigned values rather than the existing "u64" one, we can for now: * rename all internal values to use uint rather than u64 * add new function names to alias the existing u64 ones Suggested-by: Morten Br

Re: [RFC PATCH 2/7] telemetry: add uint type as alias for u64

2022-12-15 Thread Bruce Richardson
On Thu, Dec 15, 2022 at 09:49:06AM +0800, lihuisong (C) wrote: > > 在 2022/12/14 2:27, Bruce Richardson 写道: > > For future standardization on the "uint" name for unsigned values rather > > than the existing "u64" one, we can for now: > > * rename all internal values to use uint rather than u64 > >

Re: [RFC PATCH 2/7] telemetry: add uint type as alias for u64

2022-12-15 Thread Bruce Richardson
On Wed, Dec 14, 2022 at 09:38:45AM -0800, Tyler Retzlaff wrote: > On Tue, Dec 13, 2022 at 06:27:25PM +, Bruce Richardson wrote: > > For future standardization on the "uint" name for unsigned values rather > > than the existing "u64" one, we can for now: > > * rename all internal values to use u

Re: [RFC PATCH 2/7] telemetry: add uint type as alias for u64

2022-12-15 Thread Thomas Monjalon
15/12/2022 10:44, Bruce Richardson: > On Wed, Dec 14, 2022 at 09:38:45AM -0800, Tyler Retzlaff wrote: > > On Tue, Dec 13, 2022 at 06:27:25PM +, Bruce Richardson wrote: > > > For future standardization on the "uint" name for unsigned values rather > > > than the existing "u64" one, we can for no

Re: [RFC PATCH 2/7] telemetry: add uint type as alias for u64

2022-12-15 Thread Bruce Richardson
On Thu, Dec 15, 2022 at 02:36:51PM +0100, Thomas Monjalon wrote: > 15/12/2022 10:44, Bruce Richardson: > > On Wed, Dec 14, 2022 at 09:38:45AM -0800, Tyler Retzlaff wrote: > > > On Tue, Dec 13, 2022 at 06:27:25PM +, Bruce Richardson wrote: > > > > For future standardization on the "uint" name fo

Re: [RFC PATCH 2/7] telemetry: add uint type as alias for u64

2022-12-15 Thread Tyler Retzlaff
On Thu, Dec 15, 2022 at 09:44:49AM +, Bruce Richardson wrote: > On Wed, Dec 14, 2022 at 09:38:45AM -0800, Tyler Retzlaff wrote: > > On Tue, Dec 13, 2022 at 06:27:25PM +, Bruce Richardson wrote: > > > For future standardization on the "uint" name for unsigned values rather > > > than the exi

Re: [RFC PATCH 2/7] telemetry: add uint type as alias for u64

2022-12-15 Thread Tyler Retzlaff
On Thu, Dec 15, 2022 at 09:42:40AM +, Bruce Richardson wrote: > On Thu, Dec 15, 2022 at 09:49:06AM +0800, lihuisong (C) wrote: > > > > 在 2022/12/14 2:27, Bruce Richardson 写道: > > > For future standardization on the "uint" name for unsigned values rather > > > than the existing "u64" one, we ca

Re: [RFC PATCH 2/7] telemetry: add uint type as alias for u64

2022-12-19 Thread Thomas Monjalon
15/12/2022 14:58, Bruce Richardson: > On Thu, Dec 15, 2022 at 02:36:51PM +0100, Thomas Monjalon wrote: > > 15/12/2022 10:44, Bruce Richardson: > > > On Wed, Dec 14, 2022 at 09:38:45AM -0800, Tyler Retzlaff wrote: > > > > On Tue, Dec 13, 2022 at 06:27:25PM +, Bruce Richardson wrote: > > > > > Fo

Re: [RFC PATCH 2/7] telemetry: add uint type as alias for u64

2022-12-19 Thread Bruce Richardson
On Mon, Dec 19, 2022 at 11:37:19AM +0100, Thomas Monjalon wrote: > 15/12/2022 14:58, Bruce Richardson: > > On Thu, Dec 15, 2022 at 02:36:51PM +0100, Thomas Monjalon wrote: > > > 15/12/2022 10:44, Bruce Richardson: > > > > On Wed, Dec 14, 2022 at 09:38:45AM -0800, Tyler Retzlaff wrote: > > > > > On