lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 29 Sep 2020 09:18:30 +0300 From: Kalle Valo <kvalo@...eaurora.org> To: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org> Cc: Stephen Rothwell <sfr@...b.auug.org.au>, Loic Poulain <loic.poulain@...aro.org>, Networking <netdev@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, David Miller <davem@...emloft.net>, Linux Next Mailing List <linux-next@...r.kernel.org>, Govind Singh <govinds@...eaurora.org>, ath11k@...ts.infradead.org Subject: Re: linux-next: build failure after merge of the mhi tree Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org> writes: >> I was looking at commit ed39d7816885 ("bus: mhi: Remove auto-start >> option") and noticed this in the commit log: >> >> This is really up to the MHI device(channel) driver to manage the state >> of its channels. >> >> So does this mean we have to make changes in ath11k to accomodate this? > > Nope. The change is needed in the MHI client driver like qrtr which is already > taken care: https://lkml.org/lkml/2020/9/28/30 Ok, that's good. > Will make sure to include ath11k list for any future API changes. Thanks! -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Powered by blists - more mailing lists