Re: [chrony-users] libchrony patch |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] libchrony patch
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Thu, 20 Jul 2023 11:36:39 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1689845802; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=1vSlqCjhGciISezara3cKeu1nvK6jM/zoQ/T/Tnqa6c=; b=K14KemW2vuoRGZH/QKiUgu2weCViIUq446yL0gDeJ/dbpc3yvnFp+HMkK+TLUJrKHzIl0i iqQh227SXwvY9Mvj2p81h10EZT+lR0dQ3529RI9sT3pJ2EDaE0PzA/B1y6xEu+9hOtptGy P8T2MG4JciN0lYn/7Fpqs/0+s0YeB/E=
On Wed, Jul 19, 2023 at 02:05:47PM -0700, Thangalin wrote:
> index 89633f8..d78e71b 100644
> --- a/message.c
> +++ b/message.c
> @@ -502,6 +502,7 @@ struct timespec get_field_timespec(const Message *msg, int field) {
> ts.tv_nsec = ntohl(*(uint32_t *)(data + 8));
> break;
> default:
> + break;
> }
What problem is this supposed to fix? A break there shouldn't make a
difference in standard C.
Please submit patches to the -devel list.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.