search for: 602,13

...SIVAL(b,0,x); writefd(f,b,4); } @@ -573,7 +588,7 @@ void write_longint(int f, int64 x) { extern int remote_version; - char b[8]; + unsigned char b[8]; if (remote_version < 16 || x <= 0x7FFFFFFF) { write_int(f, (int)x); @@ -587,13 +602,13 @@ writefd(f,b,8); } -void write_buf(int f,char *buf,int len) +void write_buf(int f,const void *buf,int len) { writefd(f,buf,len); } /* write a string to the connection */ -static void write_sbuf(int f,char *buf) +static void write_sbuf(int f,const char *buf) {...

...char *sflags = flags & NBDKIT_FLAG_FUA ? "fua" : ""; + const char *args[] = { script, "trim", h, cbuf, obuf, sflags, NULL }; snprintf (cbuf, sizeof cbuf, "%" PRIu32, count); snprintf (obuf, sizeof obuf, "%" PRIu64, offset); @@ -538,12 +602,13 @@ sh_trim (void *handle, uint32_t count, uint64_t offset) } static int -sh_zero (void *handle, uint32_t count, uint64_t offset, int may_trim) +sh_zero (void *handle, uint32_t count, uint64_t offset, uint32_t flags) { char *h = handle; char cbuf[32], obuf[32]; - const char *args[] =...

Some feature additions to the shell script plugin allow us to test the export flags field reasonably easily. Rich.

Changes since v2: handling for devices without config space (e.g. rng) reduce # of mappings for VQs These patches seem to work fine on my virtio-1.0 qemu branch. There haven't been any bugs since v2: just minor cleanups and enhancements. QEMU side is still undergoing polishing, but is already testable. Rusty, what do you think? Let's merge these for 3.20? Also - will you be doing that

Changes since v2: handling for devices without config space (e.g. rng) reduce # of mappings for VQs These patches seem to work fine on my virtio-1.0 qemu branch. There haven't been any bugs since v2: just minor cleanups and enhancements. QEMU side is still undergoing polishing, but is already testable. Rusty, what do you think? Let's merge these for 3.20? Also - will you be doing that

Several simple framebuffer drivers copy most of the TTM code from each other. The implementation is always the same; except for the name of some data structures. As recently discussed, this patch set provides generic memory-management code for simple framebuffers with dedicated video memory. It further converts the respective drivers to the generic code. The shared code is basically the same

Several simple framebuffer drivers copy most of the TTM code from each other. The implementation is always the same; except for the name of some data structures. As recently discussed, this patch set provides generic memory-management code for simple framebuffers with dedicated video memory. It further converts the respective drivers to the generic code. The shared code is basically the same

Several simple framebuffer drivers copy most of the TTM code from each other. The implementation is always the same; except for the name of some data structures. As recently discussed, this patch set provides generic memory-management code for simple framebuffers with dedicated video memory. It further converts the respective drivers to the generic code. The shared code is basically the same

Several simple framebuffer drivers copy most of the TTM code from each other. The implementation is always the same; except for the name of some data structures. As recently discussed, this patch set provides generic memory-management code for simple framebuffers with dedicated video memory. It further converts the respective drivers to the generic code. The shared code is basically the same

Several simple framebuffer drivers copy most of the TTM code from each other. The implementation is always the same; except for the name of some data structures. As recently discussed, this patch set provides generic memory-management code for simple framebuffers with dedicated video memory. It further converts the respective drivers to the generic code. The shared code is basically the same

Several simple framebuffer drivers copy most of the TTM code from each other. The implementation is always the same; except for the name of some data structures. As recently discussed, this patch set provides generic memory-management code for simple framebuffers with dedicated video memory. It further converts the respective drivers to the generic code. The shared code is basically the same

...| OptString n + | StringList (_, n) -> pr "%s" n | Pointer (_, n) -> pr "%s" n diff --git a/generator/OCaml.ml b/generator/OCaml.ml index f0af3ae67..955da6f09 100644 --- a/generator/OCaml.ml +++ b/generator/OCaml.ml @@ -602,13 +602,7 @@ copy_table (char * const * argv) List.iter ( function - | Pathname n - | Device n | Mountable n | Dev_or_Path n | Mountable_or_Path n - | String n - | FileIn n - | FileOut n - | Key n - | GUID n -> + | String...

Very large but mechanical change to the generator. Rich.