ivi-shell: ivi-layout.c, Change wl_list_remove from wl_list_init in function of ivi_surface destruction

> This is broken. wl_list_init() will only corrupt every list here. I
> think you wanted wl_list_remove().

Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
ivi-shell: ivi-shell.c, Fix leading to bad memory write

> You destroy ivi_shell_surface here. You also need to set the userdata of
> the wl_resource to NULL, if the wl_resource still exists. Otherwise,
> shell_destroy_shell_surface() will be called later, and it will use the
> dangling pointer from the wl_resource of the ivi_surface protocol
> object, leading to bad memory write

Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
ivi-shell: ivi-shell.h, Delete never used field

> This field is never used. It didn't make sense to me at all, so I
> commented it out, and indeed things build just fine.

Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
hmi-controller: Load settings from file in init_module.

> All the above config parsing should be done during module init.
> That way, if the config parsing fails, you can propagate the failure all
> the way out of module init, which should cause Weston to exit instead of
> starting up with possibly a broken UI.

Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
hmi-controller: Post error to valid resource.

> You can't post an error on a NULL resource, Weston will crash. Instead
> of 'resource' use wl_client_get_object(client, 1).
> 1 is the protocol object id for wl_display, which always exists, and
> quite conveniently we are also sending a wl_display error code. I think
> that should work.

Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>