On Mon, 5 Mar 2018 23:11:40 +0200
"Michael S. Tsirkin" wrote:
> On Mon, Mar 05, 2018 at 05:04:40PM +0100, Cornelia Huck wrote:
> > On Mon, 5 Mar 2018 16:26:11 +0200
> > "Michael S. Tsirkin" wrote:
> >
> > > On Mon, Mar 05, 2018 at 03:20:35PM +0100, Cornelia
On Mon, Mar 05, 2018 at 05:04:40PM +0100, Cornelia Huck wrote:
> On Mon, 5 Mar 2018 16:26:11 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Mon, Mar 05, 2018 at 03:20:35PM +0100, Cornelia Huck wrote:
> > > On Wed, 28 Feb 2018 21:16:32 +0200
> > > "Michael S. Tsirkin"
On Mon, 5 Mar 2018 16:26:11 +0200
"Michael S. Tsirkin" wrote:
> On Mon, Mar 05, 2018 at 03:20:35PM +0100, Cornelia Huck wrote:
> > On Wed, 28 Feb 2018 21:16:32 +0200
> > "Michael S. Tsirkin" wrote:
> >
> > > Bitfields are a useful and familiar way to specify
On Mon, Mar 05, 2018 at 03:20:35PM +0100, Cornelia Huck wrote:
> On Wed, 28 Feb 2018 21:16:32 +0200
> "Michael S. Tsirkin" wrote:
>
> > Bitfields are a useful and familiar way to specify sub-byte structure
> > layout. The only issue is that bitfield order isn't portable across
>
On Wed, 28 Feb 2018 21:16:32 +0200
"Michael S. Tsirkin" wrote:
> Bitfields are a useful and familiar way to specify sub-byte structure
> layout. The only issue is that bitfield order isn't portable across
> architectures. Document that we list bitfields from least to
> most