Re: [PATCH] ath10k: Fix HOST capability QMI incompatibility

2019-09-17 Thread Kalle Valo
Bjorn Andersson wrote: > The introduction of 768ec4c012ac ("ath10k: update HOST capability QMI > message") served the purpose of supporting the new and extended HOST > capability QMI message. > > But while the new message adds a slew of optional members it changes the > data type of the "daemon_

Re: [PATCH] ath10k: Fix HOST capability QMI incompatibility

2019-09-17 Thread Kalle Valo
Bjorn Andersson wrote: > The introduction of 768ec4c012ac ("ath10k: update HOST capability QMI > message") served the purpose of supporting the new and extended HOST > capability QMI message. > > But while the new message adds a slew of optional members it changes the > data type of the "daemon_

Re: [PATCH] ath10k: Fix HOST capability QMI incompatibility

2019-08-16 Thread Rob Herring
On Wed, Jul 24, 2019 at 11:31:08PM -0700, Bjorn Andersson wrote: > The introduction of 768ec4c012ac ("ath10k: update HOST capability QMI > message") served the purpose of supporting the new and extended HOST > capability QMI message. > > But while the new message adds a slew of optional members it

[PATCH] ath10k: Fix HOST capability QMI incompatibility

2019-07-24 Thread Bjorn Andersson
The introduction of 768ec4c012ac ("ath10k: update HOST capability QMI message") served the purpose of supporting the new and extended HOST capability QMI message. But while the new message adds a slew of optional members it changes the data type of the "daemon_support" member, which means that old