On Thu, Dec 15, 2022 at 09:41:38AM +, Bruce Richardson wrote:
> On Wed, Dec 14, 2022 at 09:30:05AM -0800, Tyler Retzlaff wrote:
> > On Tue, Dec 13, 2022 at 06:27:24PM +, Bruce Richardson wrote:
> > > For telemetry data, rather than having unsigned 64-bit values and signed
> > > 32-bit value
On Wed, Dec 14, 2022 at 09:30:05AM -0800, Tyler Retzlaff wrote:
> On Tue, Dec 13, 2022 at 06:27:24PM +, Bruce Richardson wrote:
> > For telemetry data, rather than having unsigned 64-bit values and signed
> > 32-bit values, we want to just have unsigned and signed values, each
> > stored with t
On Tue, Dec 13, 2022 at 06:27:24PM +, Bruce Richardson wrote:
> For telemetry data, rather than having unsigned 64-bit values and signed
> 32-bit values, we want to just have unsigned and signed values, each
> stored with the max bit-width i.e. 64-bits. To that end, we rename the
> U64 enum ent
For telemetry data, rather than having unsigned 64-bit values and signed
32-bit values, we want to just have unsigned and signed values, each
stored with the max bit-width i.e. 64-bits. To that end, we rename the
U64 enum entry to "UINT" to have a more generic name
For backward API-level compatibi
4 matches
Mail list logo
