linux-next: Tree for Jan 19

Hi all, Changes since 20210118: The hid tree gained a conflict against the qcom tree. The drm tree still had its build failure so I used the version from next-20210107. The drm-intel tree still had its build failure from merging the drm tree, so I have used the version from next-20210108. I

linux-next: Tree for Jan 19

Hi all, News: there will probably be very few, if any, releases next week as LCA is on (unfortunate clash with the merge window). Changes since 20180118: The powerpc tree gained a build failure due to an interaction with Linus' tree, so I applied a merge fix patch. It gained another for which

linux-next: Tree for Jan 19

Hi all, News: there will probably be very few, if any, releases next week as LCA is on (unfortunate clash with the merge window). Changes since 20180118: The powerpc tree gained a build failure due to an interaction with Linus' tree, so I applied a merge fix patch. It gained another for which

Re: linux-next: Tree for Jan 19

[Re: linux-next: Tree for Jan 19] On 27/01/2017 (Fri 00:08) Stafford Horne wrote: > On Thu, Jan 26, 2017 at 02:45:15PM +0900, Stafford Horne wrote: > > On Wed, Jan 25, 2017 at 11:37:11AM -0500, Paul Gortmaker wrote: > > > [Re: linux-next: Tree for Jan 19] On 23/01/2017 (M

Re: linux-next: Tree for Jan 19

[Re: linux-next: Tree for Jan 19] On 27/01/2017 (Fri 00:08) Stafford Horne wrote: > On Thu, Jan 26, 2017 at 02:45:15PM +0900, Stafford Horne wrote: > > On Wed, Jan 25, 2017 at 11:37:11AM -0500, Paul Gortmaker wrote: > > > [Re: linux-next: Tree for Jan 19] On 23/01/2017 (M

Re: linux-next: Tree for Jan 19

On Thu, Jan 26, 2017 at 02:45:15PM +0900, Stafford Horne wrote: > On Wed, Jan 25, 2017 at 11:37:11AM -0500, Paul Gortmaker wrote: > > [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne > > wrote: > > > > [...] > > > > > > >

Re: linux-next: Tree for Jan 19

On Thu, Jan 26, 2017 at 02:45:15PM +0900, Stafford Horne wrote: > On Wed, Jan 25, 2017 at 11:37:11AM -0500, Paul Gortmaker wrote: > > [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne > > wrote: > > > > [...] > > > > > > >

Re: linux-next: Tree for Jan 19

[Re: linux-next: Tree for Jan 19] On 26/01/2017 (Thu 06:22) Guenter Roeck wrote: > On 01/25/2017 09:38 PM, Stafford Horne wrote: > >On Wed, Jan 25, 2017 at 08:54:53PM -0800, Guenter Roeck wrote: > >>On 01/25/2017 08:37 AM, Paul Gortmaker wrote: > >>>[Re: linux-next:

Re: linux-next: Tree for Jan 19

[Re: linux-next: Tree for Jan 19] On 26/01/2017 (Thu 06:22) Guenter Roeck wrote: > On 01/25/2017 09:38 PM, Stafford Horne wrote: > >On Wed, Jan 25, 2017 at 08:54:53PM -0800, Guenter Roeck wrote: > >>On 01/25/2017 08:37 AM, Paul Gortmaker wrote: > >>>[Re: linux-next:

Re: linux-next: Tree for Jan 19

On 01/25/2017 09:38 PM, Stafford Horne wrote: On Wed, Jan 25, 2017 at 08:54:53PM -0800, Guenter Roeck wrote: On 01/25/2017 08:37 AM, Paul Gortmaker wrote: [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne wrote: [...] Are all of these builds using the tests from

Re: linux-next: Tree for Jan 19

On 01/25/2017 09:38 PM, Stafford Horne wrote: On Wed, Jan 25, 2017 at 08:54:53PM -0800, Guenter Roeck wrote: On 01/25/2017 08:37 AM, Paul Gortmaker wrote: [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne wrote: [...] Are all of these builds using the tests from

Re: linux-next: Tree for Jan 19

On Wed, Jan 25, 2017 at 11:37:11AM -0500, Paul Gortmaker wrote: > [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne > wrote: > > [...] > > > > > Are all of these builds using the tests from lkp-tests [0]? > > Not using any spe

Re: linux-next: Tree for Jan 19

On Wed, Jan 25, 2017 at 11:37:11AM -0500, Paul Gortmaker wrote: > [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne > wrote: > > [...] > > > > > Are all of these builds using the tests from lkp-tests [0]? > > Not using any spe

Re: linux-next: Tree for Jan 19

On Wed, Jan 25, 2017 at 08:54:53PM -0800, Guenter Roeck wrote: > On 01/25/2017 08:37 AM, Paul Gortmaker wrote: > > [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne > > wrote: > > > > [...] > > > > > > > > Are al

Re: linux-next: Tree for Jan 19

On Wed, Jan 25, 2017 at 08:54:53PM -0800, Guenter Roeck wrote: > On 01/25/2017 08:37 AM, Paul Gortmaker wrote: > > [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne > > wrote: > > > > [...] > > > > > > > > Are al

Re: linux-next: Tree for Jan 19

On 01/25/2017 08:37 AM, Paul Gortmaker wrote: [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne wrote: [...] Are all of these builds using the tests from lkp-tests [0]? Not using any specific tests, other than compiling allmodconfig and defconfig. If so

Re: linux-next: Tree for Jan 19

On 01/25/2017 08:37 AM, Paul Gortmaker wrote: [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne wrote: [...] Are all of these builds using the tests from lkp-tests [0]? Not using any specific tests, other than compiling allmodconfig and defconfig. If so

Re: linux-next: Tree for Jan 19

[Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne wrote: [...] > > Are all of these builds using the tests from lkp-tests [0]? Not using any specific tests, other than compiling allmodconfig and defconfig. > > If so and no one is working on openri

Re: linux-next: Tree for Jan 19

[Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne wrote: [...] > > Are all of these builds using the tests from lkp-tests [0]? Not using any specific tests, other than compiling allmodconfig and defconfig. > > If so and no one is working on openri

Re: linux-next: Tree for Jan 19

On Thu, Jan 19, 2017 at 11:42:45AM -0500, Paul Gortmaker wrote: > On Thu, Jan 19, 2017 at 12:39 AM, Stephen Rothwell > wrote: > > Hi all, > > > > Changes since 20170118: > > > > The audit tree gained a conflict against Linus' tree. > > > > The tip tree gained a conflict

Re: linux-next: Tree for Jan 19

On Thu, Jan 19, 2017 at 11:42:45AM -0500, Paul Gortmaker wrote: > On Thu, Jan 19, 2017 at 12:39 AM, Stephen Rothwell > wrote: > > Hi all, > > > > Changes since 20170118: > > > > The audit tree gained a conflict against Linus' tree. > > > > The tip tree gained a conflict against the security

Re: linux-next: Tree for Jan 19

Hi Paul, On Thu, Jan 19, 2017 at 11:42:45AM -0500, Paul Gortmaker wrote: > On Thu, Jan 19, 2017 at 12:39 AM, Stephen Rothwell > wrote: > > Hi all, > > > > Changes since 20170118: > > > > The audit tree gained a conflict against Linus' tree. > > > > The tip tree gained a

Re: linux-next: Tree for Jan 19

Hi Paul, On Thu, Jan 19, 2017 at 11:42:45AM -0500, Paul Gortmaker wrote: > On Thu, Jan 19, 2017 at 12:39 AM, Stephen Rothwell > wrote: > > Hi all, > > > > Changes since 20170118: > > > > The audit tree gained a conflict against Linus' tree. > > > > The tip tree gained a conflict against the

Re: linux-next: Tree for Jan 19

On Thu, Jan 19, 2017 at 12:39 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20170118: > > The audit tree gained a conflict against Linus' tree. > > The tip tree gained a conflict against the security tree. > > The rcu tree gained a semantic conflict against the

Re: linux-next: Tree for Jan 19

On Thu, Jan 19, 2017 at 12:39 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20170118: > > The audit tree gained a conflict against Linus' tree. > > The tip tree gained a conflict against the security tree. > > The rcu tree gained a semantic conflict against the net-next tree for >

linux-next: Tree for Jan 19

Hi all, Changes since 20170118: The audit tree gained a conflict against Linus' tree. The tip tree gained a conflict against the security tree. The rcu tree gained a semantic conflict against the net-next tree for which I applied a merge fix patch. I dropped 4 patches from the akpm tree that

linux-next: Tree for Jan 19

Hi all, Changes since 20170118: The audit tree gained a conflict against Linus' tree. The tip tree gained a conflict against the security tree. The rcu tree gained a semantic conflict against the net-next tree for which I applied a merge fix patch. I dropped 4 patches from the akpm tree that

linux-next: Tree for Jan 19

Hi all, Changes since 20150116: The i2c tree lost its build failure. The net-next tree gained a build failure so I used the version from next-20150116 for today. The luto-misc tree gained a conflict against the tip tree. The akpm-current tree gained two build failures for which I added fix

linux-next: Tree for Jan 19

Hi all, Changes since 20150116: The i2c tree lost its build failure. The net-next tree gained a build failure so I used the version from next-20150116 for today. The luto-misc tree gained a conflict against the tip tree. The akpm-current tree gained two build failures for which I added fix