Re: [PATCH gnumach] Use c_string for dev_name_t in the device subsystem.

Applied, thanks! Flavio Cruz, le mer. 26 avril 2023 01:22:53 -0400, a ecrit: > Added device_open_new and device_open_new_request and reused the old MiG > ID for xxx_device_set_status which has not been in used in the past > decade. > > Note that device_open_new is gated on defining > DEVICE_ENABL

Re: [PATCH gnumach] Use c_string for dev_name_t in the device subsystem.

Hi Sergey On Wed, Apr 26, 2023 at 01:43:55PM +0300, Sergey Bugaev wrote: Hi Flavio, could you please explain what the difference / the advantage of new_dev_name_t is over dev_name_t? (Preferably, put it into the commit message too.) tl;dr; we can get rid of mach_msg_type_long_t on x86_64. Lo

Re: [PATCH gnumach] Use c_string for dev_name_t in the device subsystem.

Hi Flavio, could you please explain what the difference / the advantage of new_dev_name_t is over dev_name_t? (Preferably, put it into the commit message too.) Isn't c_string same as MACH_MSG_TYPE_STRING_C? What are we gaining? What is your overall plan concerning string handling in RPCs? The tw

[PATCH gnumach] Use c_string for dev_name_t in the device subsystem.

Added device_open_new and device_open_new_request and reused the old MiG ID for xxx_device_set_status which has not been in used in the past decade. Note that device_open_new is gated on defining DEVICE_ENABLE_DEVICE_OPEN_NEW because otherwise some hurd servers wouldn't compile anymore unless patc