Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1482666
| From | Olaf Hering <olaf@aepfle.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 3/3] Drivers: hv: utils: Support TimeSync version 4.0 protocol samples. |
| Date | 2016-09-13 19:40 +0200 |
| Message-ID | <sgZQB-4ZB-7@gated-at.bofh.it> (permalink) |
| References | <sf4Up-4Eh-5@gated-at.bofh.it> <sf4Up-4Eh-7@gated-at.bofh.it> <sf4Uq-4Eh-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Thu, Sep 08, kys@exchange.microsoft.com wrote: > - default: > + case(VERSION_WIN10): > util_fw_version = UTIL_FW_VERSION; > sd_srv_version = SD_VERSION; > ts_srv_version = TS_VERSION; > hb_srv_version = HB_VERSION; > + break; > + default: > + util_fw_version = UTIL_FW_VERSION; > + sd_srv_version = SD_VERSION; > + ts_srv_version = TS_VERSION_3; > + hb_srv_version = HB_VERSION; Is this correct? An old kernel on a newer host would use the old protocol. I assume that new host will also know about the old protocol? Perhaps a better approach would be to list the known existing hosts and use the new protocol for upcoming, unknown hosts via 'default:'. Olaf
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [PATCH 3/3] Drivers: hv: utils: Support TimeSync version 4.0 protocol samples. Olaf Hering <olaf@aepfle.de> - 2016-09-13 19:40 +0200
RE: [PATCH 3/3] Drivers: hv: utils: Support TimeSync version 4.0 protocol samples. "Alex Ng (LIS)" <alexng@microsoft.com> - 2016-09-13 22:10 +0200
Re: [PATCH 3/3] Drivers: hv: utils: Support TimeSync version 4.0 protocol samples. Olaf Hering <olaf@aepfle.de> - 2016-09-14 15:10 +0200
csiph-web