* device/dev_pager.c (device_pager_data_request_done) (memset) (io_residual):
Cast to size_t instead to unsigned.
---
device/dev_pager.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/device/dev_pager.c b/device/dev_pager.c
index b9796ca..7c3e088 100644
--- a/device/dev_page
The situation is that there is a pointer (source) that is being cast to
another pointer (target) and then the members of the target structure
pointed to by the target pointer are being used as if the content of
memory at the source address is a target structure, not source structure
pointed to by
Variable pager is already of ipc_port_t type.
* device/dev_pager.c: Remove unnecessary casts.
---
device/dev_pager.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/device/dev_pager.c b/device/dev_pager.c
index 97e417e..b9796ca 100644
--- a/device/dev_pager.c
+++ b/device
Avoid the casts by passing the address of the links thread
structure member to enqueue_tail().
* kern/sched_prim.c: Avoid casts.
---
kern/sched_prim.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kern/sched_prim.c b/kern/sched_prim.c
index c06cd77..ec041fc 100644
---
> Justus Winter <4win...@informatik.uni-hamburg.de> writes:
> * utils/rpctrace.c (escape_sequences): New char array mapping
> characters to their escape sequence.
[…]
> +static char escape_sequences[0xff] =
JFTR: [0xFF] means [0] through [0xFE]. My guess would be that
it
Currently, it is impossible to properly attribute response messages to
requests. Even though rpctrace is single-threaded, its tracee may
not. Or there might be more than one tracee. In any such case it is
not guaranteed that the reply message we just processed is for the
request we just printed.
* utils/rpctrace.c (escape_sequences): New char array mapping
characters to their escape sequence.
(print_data): Escape non-printable characters when printing strings.
---
utils/rpctrace.c | 48 ++--
1 file changed, 46 insertions(+), 2 deletions(-)
di
Justus Winter, le Fri 13 Dec 2013 10:13:00 +0100, a écrit :
> mount uses libblkid (if available) to detect the file system type when
> using mount -t auto. libblkid calls fat file systems "vfat", our fat
> translator is called "fatfs". Fix this discrepancy in mount.
Ack.
> * utils/mount.c (do_m
mount uses libblkid (if available) to detect the file system type when
using mount -t auto. libblkid calls fat file systems "vfat", our fat
translator is called "fatfs". Fix this discrepancy in mount.
* utils/mount.c (do_mount): Fix autodetection of fat file systems.
---
utils/mount.c |7 ++
