Re: linux-next: build failure after merge of the mhi tree

Hi Manivannan, On Wed, 18 Nov 2020 15:09:00 +0530 Manivannan Sadhasivam wrote: > > Patch applied to immutable branch and merged into mhi-next. Now you can > remove the fix patch. Thanks for letting me know. -- Cheers, Stephen Rothwell pgpkekgfT7n1i.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the mhi tree

On Wed, Nov 18, 2020 at 10:36:40AM +0530, Manivannan Sadhasivam wrote: > Hi Stephen, > > On Wed, Nov 18, 2020 at 03:51:28PM +1100, Stephen Rothwell wrote: > > Hi all, > > > > On Wed, 18 Nov 2020 15:45:00 +1100 Stephen Rothwell > > wrote: > > > > > > On Wed, 18 Nov 2020 15:39:12 +1100 Stephen Ro

Re: linux-next: build failure after merge of the mhi tree

Hi Stephen, On Wed, Nov 18, 2020 at 03:51:28PM +1100, Stephen Rothwell wrote: > Hi all, > > On Wed, 18 Nov 2020 15:45:00 +1100 Stephen Rothwell > wrote: > > > > On Wed, 18 Nov 2020 15:39:12 +1100 Stephen Rothwell > > wrote: > > > > > > Why isn't that "fix patch" in the mhi tree (with necessar

Re: linux-next: build failure after merge of the mhi tree

Hi all, On Wed, 18 Nov 2020 15:45:00 +1100 Stephen Rothwell wrote: > > On Wed, 18 Nov 2020 15:39:12 +1100 Stephen Rothwell > wrote: > > > > Why isn't that "fix patch" in the mhi tree (with necessary Acked-bys)? > > Ignore that, I missed its appearance :-) Ignore that, my question stands (g

Re: linux-next: build failure after merge of the mhi tree

Hi all, On Wed, 18 Nov 2020 15:39:12 +1100 Stephen Rothwell wrote: > > Why isn't that "fix patch" in the mhi tree (with necessary Acked-bys)? Ignore that, I missed its appearance :-) -- Cheers, Stephen Rothwell pgpiUFU2hM2C_.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the mhi tree

Hi Manivannan, On Tue, 17 Nov 2020 09:53:59 +0530 Manivannan Sadhasivam wrote: > > +ath11k list, kalle > > On Tue, Nov 17, 2020 at 03:12:25PM +1100, Stephen Rothwell wrote: > > Hi all, > > > > After merging the mhi tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > >

Re: linux-next: build failure after merge of the mhi tree

Manivannan Sadhasivam writes: > On Tue, Nov 17, 2020 at 09:53:59AM +0530, Manivannan Sadhasivam wrote: >> +ath11k list, kalle >> > > Oops... adding now > >> On Tue, Nov 17, 2020 at 03:12:25PM +1100, Stephen Rothwell wrote: >> > Hi all, >> > >> > After merging the mhi tree, today's linux-next bu

Re: linux-next: build failure after merge of the mhi tree

On Tue, Nov 17, 2020 at 09:53:59AM +0530, Manivannan Sadhasivam wrote: > +ath11k list, kalle > Oops... adding now > On Tue, Nov 17, 2020 at 03:12:25PM +1100, Stephen Rothwell wrote: > > Hi all, > > > > After merging the mhi tree, today's linux-next build (x86_64 allmodconfig) > > failed like th

Re: linux-next: build failure after merge of the mhi tree

+ath11k list, kalle On Tue, Nov 17, 2020 at 03:12:25PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the mhi tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > drivers/net/wireless/ath/ath11k/mhi.c:27:4: error: 'struct > mhi_channel_config' has no member n

linux-next: build failure after merge of the mhi tree

Hi all, After merging the mhi tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/ath/ath11k/mhi.c:27:4: error: 'struct mhi_channel_config' has no member named 'auto_start' 27 | .auto_start = false, |^~ drivers/net/wireless/ath/ath11

Re: linux-next: build failure after merge of the mhi tree

Hi, On Mon, Sep 28, 2020 at 06:42:30PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the mhi tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > drivers/net/wireless/ath/ath11k/mhi.c:27:4: error: 'struct > mhi_channel_config' has no member named 'auto_start

Re: linux-next: build failure after merge of the mhi tree

Manivannan Sadhasivam 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 c

Re: linux-next: build failure after merge of the mhi tree

On Mon, Sep 28, 2020 at 07:45:37PM +0300, Kalle Valo wrote: > Manivannan Sadhasivam writes: > > > On Mon, Sep 28, 2020 at 12:34:40PM +0300, Kalle Valo wrote: > >> Manivannan Sadhasivam writes: > >> > >> > On Mon, Sep 28, 2020 at 06:42:30PM +1000, Stephen Rothwell wrote: > >> >> Hi all, > >> >>

Re: linux-next: build failure after merge of the mhi tree

Manivannan Sadhasivam writes: > On Mon, Sep 28, 2020 at 12:34:40PM +0300, Kalle Valo wrote: >> Manivannan Sadhasivam writes: >> >> > On Mon, Sep 28, 2020 at 06:42:30PM +1000, Stephen Rothwell wrote: >> >> Hi all, >> >> >> >> After merging the mhi tree, today's linux-next build (x86_64 allmodco

Re: linux-next: build failure after merge of the mhi tree

On Mon, Sep 28, 2020 at 12:34:40PM +0300, Kalle Valo wrote: > Manivannan Sadhasivam writes: > > > On Mon, Sep 28, 2020 at 06:42:30PM +1000, Stephen Rothwell wrote: > >> Hi all, > >> > >> After merging the mhi tree, today's linux-next build (x86_64 allmodconfig) > >> failed like this: > >> > >>

Re: linux-next: build failure after merge of the mhi tree

Manivannan Sadhasivam writes: > On Mon, Sep 28, 2020 at 06:42:30PM +1000, Stephen Rothwell wrote: >> Hi all, >> >> After merging the mhi tree, today's linux-next build (x86_64 allmodconfig) >> failed like this: >> >> drivers/net/wireless/ath/ath11k/mhi.c:27:4: error: 'struct >> mhi_channel_conf

Re: linux-next: build failure after merge of the mhi tree

Hi Manivannan, On Mon, 28 Sep 2020 14:40:35 +0530 Manivannan Sadhasivam wrote: > > But your change looks good and I can just modify the subject/description and > resubmit. Or if Dave prefers to fix the original commit itself in net-next, > I'm fine! Dave never rebase the net-next tree, so a new

Re: linux-next: build failure after merge of the mhi tree

Hi, On Mon, Sep 28, 2020 at 06:42:30PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the mhi tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > drivers/net/wireless/ath/ath11k/mhi.c:27:4: error: 'struct > mhi_channel_config' has no member named 'auto_start

linux-next: build failure after merge of the mhi tree

Hi all, After merging the mhi tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/ath/ath11k/mhi.c:27:4: error: 'struct mhi_channel_config' has no member named 'auto_start' 27 | .auto_start = false, |^~ drivers/net/wireless/ath/ath11

Re: linux-next: build failure after merge of the mhi tree

Hi all, On Wed, 19 Aug 2020 09:34:55 +0530 Manivannan Sadhasivam wrote: > > On Wed, Aug 19, 2020 at 01:48:00PM +1000, Stephen Rothwell wrote: > > > > After merging the mhi tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > I am not sure which commit(s) caused t

Re: linux-next: build failure after merge of the mhi tree

Hi Stephen, On Wed, Aug 19, 2020 at 01:48:00PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the mhi tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > > I am not sure which commit(s) caused this. > Probably the below commit which built fine with gcc but

Re: linux-next: build failure after merge of the mhi tree

Hi all, On Wed, 19 Aug 2020 13:48:00 +1000 Stephen Rothwell wrote: > > After merging the mhi tree, today's linux-next build (x86_64 allmodconfig) > failed like this: WARNING: modpost: missing MODULE_LICENSE() in drivers/bus/mhi/core/main.o WARNING: modpost: missing MODULE_LICENSE() in drivers/

linux-next: build failure after merge of the mhi tree

Hi all, After merging the mhi tree, today's linux-next build (x86_64 allmodconfig) failed like this: I am not sure which commit(s) caused this. I have used the mhi tree from next-20200818 for today. -- Cheers, Stephen Rothwell pgpd3gORS3Gqv.pgp Description: OpenPGP digital signature