linux-next: Tree for Oct 9th

linux-next: Tree for Oct 9th

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]

For my birthday I've gone and got myself a linux-next tree:

Changes since 20170929:

The net-next and drm trees lost their build failures but the rcu tree
gained one.

I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log
files in the Next directory.  Between each merge, the tree was built
with an arm64 defconfig, an allmodconfig (with
CONFIG_BUILD_DOCSRC=n) for x86_64, a multi_v7_defconfig for arm and a
native build of tools/perf. After the final fixups (if any), I do an
x86_64 modules_install followed by builds for x86_64 allnoconfig,
and arm64 allnoconfig 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: Tree for Oct 9th (drivers/dma/stm32-mdma.c)

[Randy Dunlap]

On 10/09/17 14:21, Mark Brown wrote:
> For my birthday I've gone and got myself a linux-next tree:
> 
> Changes since 20170929:
> 

on i386:

drivers/dma/stm32-mdma.o: In function `stm32_mdma_prep_dma_memcpy':
stm32-mdma.c:(.text+0x1174): undefined reference to `__umoddi3'
stm32-mdma.c:(.text+0x1208): undefined reference to `__umoddi3'
stm32-mdma.c:(.text+0x134c): undefined reference to `__umoddi3'
stm32-mdma.c:(.text+0x141d): undefined reference to `__umoddi3'



-- 
~Randy

Re: linux-next: Tree for Oct 9th (of: unittest: testcases)

[Randy Dunlap]

On 10/09/17 14:21, Mark Brown wrote:
> For my birthday I've gone and got myself a linux-next tree:
> 
> Changes since 20170929:
> 
> The net-next and drm trees lost their build failures but the rcu tree
> gained one.


I don't know what this is but it's new AFAIK.
(seen on i386 and x86_64)


  DTC     drivers/of/unittest-data/testcases.dtb
drivers/of/unittest-data/testcases.dtb: Warning (interrupts_extended_property): Could not get phandle node for /__local_fixups__/testcase-data/interrupts/interrupts-extended0:interrupts-extended(cell 3)
drivers/of/unittest-data/testcases.dtb: Warning (interrupts_property): interrupts size is (4), expected multiple of 8 in /testcase-data/testcase-device2



-- 
~Randy

Re: linux-next: Tree for Oct 9th (of: unittest: testcases)

[Rob Herring]

+Frank

On Tue, Oct 10, 2017 at 12:33 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
> On 10/09/17 14:21, Mark Brown wrote:
>> For my birthday I've gone and got myself a linux-next tree:
>>
>> Changes since 20170929:
>>
>> The net-next and drm trees lost their build failures but the rcu tree
>> gained one.
>
>
> I don't know what this is but it's new AFAIK.
> (seen on i386 and x86_64)

Yes, new dtc version with new warnings.

>   DTC     drivers/of/unittest-data/testcases.dtb
> drivers/of/unittest-data/testcases.dtb: Warning (interrupts_extended_property): Could not get phandle node for /__local_fixups__/testcase-data/interrupts/interrupts-extended0:interrupts-extended(cell 3)

Frank, this is in __local_fixups__, we should be able to remove that
now as the necessary dtc changes are in place, right?

> drivers/of/unittest-data/testcases.dtb: Warning (interrupts_property): interrupts size is (4), expected multiple of 8 in /testcase-data/testcase-device2

This one is purposely bad data to feed the unit test. If I suppress
it, then it is suppressed everywhere in the unit test data.

Rob

Re: linux-next: Tree for Oct 9th (of: unittest: testcases)

[Randy Dunlap]

On 10/10/17 11:26, Rob Herring wrote:
> +Frank
> 
> On Tue, Oct 10, 2017 at 12:33 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
>> On 10/09/17 14:21, Mark Brown wrote:
>>> For my birthday I've gone and got myself a linux-next tree:
>>>
>>> Changes since 20170929:
>>>
>>> The net-next and drm trees lost their build failures but the rcu tree
>>> gained one.
>>
>>
>> I don't know what this is but it's new AFAIK.
>> (seen on i386 and x86_64)
> 
> Yes, new dtc version with new warnings.
> 
>>   DTC     drivers/of/unittest-data/testcases.dtb
>> drivers/of/unittest-data/testcases.dtb: Warning (interrupts_extended_property): Could not get phandle node for /__local_fixups__/testcase-data/interrupts/interrupts-extended0:interrupts-extended(cell 3)
> 
> Frank, this is in __local_fixups__, we should be able to remove that
> now as the necessary dtc changes are in place, right?
> 
>> drivers/of/unittest-data/testcases.dtb: Warning (interrupts_property): interrupts size is (4), expected multiple of 8 in /testcase-data/testcase-device2
> 
> This one is purposely bad data to feed the unit test. If I suppress
> it, then it is suppressed everywhere in the unit test data.

Thanks for the info.


-- 
~Randy

linux-next: No tree for Oct 10th

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 230 bytes --]

There will be no -next today, too many of the failures came when I had
to step away from the computer and I'm out of time.  Sorry, I'll give it
another go tomorrow.  

There were new failures in drm-intel-fixes and keystone.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: Tree for Oct 9th (drivers/dma/stm32-mdma.c)

[Vinod Koul]

On Tue, Oct 10, 2017 at 09:27:18AM -0700, Randy Dunlap wrote:
> On 10/09/17 14:21, Mark Brown wrote:
> > For my birthday I've gone and got myself a linux-next tree:

Nice thing you chose to do for the day :D

> > 
> > Changes since 20170929:
> > 
> 
> on i386:
> 
> drivers/dma/stm32-mdma.o: In function `stm32_mdma_prep_dma_memcpy':
> stm32-mdma.c:(.text+0x1174): undefined reference to `__umoddi3'
> stm32-mdma.c:(.text+0x1208): undefined reference to `__umoddi3'
> stm32-mdma.c:(.text+0x134c): undefined reference to `__umoddi3'
> stm32-mdma.c:(.text+0x141d): undefined reference to `__umoddi3'

The driver uses DIV_ROUND_UP but this should have worked, let me check more.
Was generic i386 defconfig used or some other config

-- 
~Vinod

Re: linux-next: Tree for Oct 9th (drivers/dma/stm32-mdma.c)

[Randy Dunlap]

On 10/11/17 05:55, Vinod Koul wrote:
> On Tue, Oct 10, 2017 at 09:27:18AM -0700, Randy Dunlap wrote:
>> On 10/09/17 14:21, Mark Brown wrote:
>>> For my birthday I've gone and got myself a linux-next tree:
> 
> Nice thing you chose to do for the day :D
> 
>>>
>>> Changes since 20170929:
>>>
>>
>> on i386:
>>
>> drivers/dma/stm32-mdma.o: In function `stm32_mdma_prep_dma_memcpy':
>> stm32-mdma.c:(.text+0x1174): undefined reference to `__umoddi3'
>> stm32-mdma.c:(.text+0x1208): undefined reference to `__umoddi3'
>> stm32-mdma.c:(.text+0x134c): undefined reference to `__umoddi3'
>> stm32-mdma.c:(.text+0x141d): undefined reference to `__umoddi3'
> 
> The driver uses DIV_ROUND_UP but this should have worked, let me check more.
> Was generic i386 defconfig used or some other config

Maybe look at the uses of '%' (modulus, as in __umoddi3).

-- 
~Randy

Re: linux-next: Tree for Oct 9th (of: unittest: testcases)

[Frank Rowand]

On 10/10/17 11:26, Rob Herring wrote:
> +Frank
> 
> On Tue, Oct 10, 2017 at 12:33 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
>> On 10/09/17 14:21, Mark Brown wrote:
>>> For my birthday I've gone and got myself a linux-next tree:
>>>
>>> Changes since 20170929:
>>>
>>> The net-next and drm trees lost their build failures but the rcu tree
>>> gained one.
>>
>>
>> I don't know what this is but it's new AFAIK.
>> (seen on i386 and x86_64)
> 
> Yes, new dtc version with new warnings.
> 
>>   DTC     drivers/of/unittest-data/testcases.dtb
>> drivers/of/unittest-data/testcases.dtb: Warning (interrupts_extended_property): Could not get phandle node for /__local_fixups__/testcase-data/interrupts/interrupts-extended0:interrupts-extended(cell 3)
> 
> Frank, this is in __local_fixups__, we should be able to remove that
> now as the necessary dtc changes are in place, right?

Yes, I have a patch to add "/plugin/;" to testcases.dts and remove the __local_fixups__ node,
but have not submitted it yet.

It builds and the unit tests still work.

I still need to rework all of the overlays that are hand coded in testcases.dts,
and was planning to do that before submitting the above changes.

-Frank

> 
>> drivers/of/unittest-data/testcases.dtb: Warning (interrupts_property): interrupts size is (4), expected multiple of 8 in /testcase-data/testcase-device2
> 
> This one is purposely bad data to feed the unit test. If I suppress
> it, then it is suppressed everywhere in the unit test data.
> 
> Rob
> .
>