linux-next: Tree for Jul 1

2020-06-30 Thread Stephen Rothwell
Hi all, Changes since 20200630: My fixes tree contains: dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning") b236d81d9e4f ("powerpc/boot/dts: Fix dtc "pciex" warnings") The tip tree still had one build failure for which I reverted a commit. The rcu tree gained a conflict against

linux-next: Tree for Jul 1

2019-07-01 Thread Stephen Rothwell
Hi all, Changes since 20190628: The dma-mapping tree gained a conflict against Linus' tree. The xfs tree gained conflicts against the f2fs tree and a build failure so I used the version from next-20190628. The pm tree gained a conflict against the pci tree and a build failure, so I used the ver

linux-next: Tree for Jul 1

2016-06-30 Thread Stephen Rothwell
Hi all, Changes since 20160630: New tree: freevxfs The powerpc tree gained a build failure for which I applied a fix patch. The pci tree gained a conflict against the tegra tree. The lightnvm tree still had its build failure so I used the version from next-20160629. The akpm-current tree gain

linux-next: Tree for Jul 1

2015-06-30 Thread Stephen Rothwell
Hi all, Please do not add any v4.3 related material to your linux-next included branches until after v4.2-rc1 is released. Changes since 20150630: I fixed a supplied patch to the akpm tree. Non-merge commits (relative to Linus' tree): 1860 1686 files changed, 98175 insertions(+), 25316 deletio

linux-next: Tree for Jul 1

2014-06-30 Thread Stephen Rothwell
Hi all, The powerpc allyesconfig is again broken more than usual. Changes since 20140630: My fixes tree contains: powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64 The net-next tree lost its build failure. The staging tree still had its build failure for which I disabled a drive

Re: Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]

2013-09-25 Thread Michael S. Tsirkin
On Wed, Sep 25, 2013 at 09:56:52AM +0200, Daniel Vetter wrote: > On Wed, Sep 25, 2013 at 01:17:52PM +1000, Dave Airlie wrote: > > On Mon, Sep 23, 2013 at 12:14 AM, Michael S. Tsirkin > > wrote: > > > On Mon, Aug 26, 2013 at 04:05:11PM +0300, Michael S. Tsirkin wrote: > > >> On Wed, Aug 21, 2013 a

Re: Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]

2013-09-25 Thread Daniel Vetter
On Wed, Sep 25, 2013 at 01:17:52PM +1000, Dave Airlie wrote: > On Mon, Sep 23, 2013 at 12:14 AM, Michael S. Tsirkin wrote: > > On Mon, Aug 26, 2013 at 04:05:11PM +0300, Michael S. Tsirkin wrote: > >> On Wed, Aug 21, 2013 at 11:22:58AM +0200, Sedat Dilek wrote: > >> > [ Re: [Intel-gfx] i915 produci

Re: Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]

2013-09-24 Thread Dave Airlie
On Mon, Sep 23, 2013 at 12:14 AM, Michael S. Tsirkin wrote: > On Mon, Aug 26, 2013 at 04:05:11PM +0300, Michael S. Tsirkin wrote: >> On Wed, Aug 21, 2013 at 11:22:58AM +0200, Sedat Dilek wrote: >> > [ Re: [Intel-gfx] i915 producing warnings with kernel 3.11-rc5 ] >> > >> > Hi, >> > >> > saw your p

Re: Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]

2013-09-22 Thread Michael S. Tsirkin
7. I still see this with 3.11. Following this message, my VGA monitor goes blank and shows an error suggesting a wrong resolution or frequency are set. Anyone? > > > > > -- Forwarded message ------ > > From: Sedat Dilek > > Date: Tue, Jul 2, 2013 at 7:3

Re: Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]

2013-08-26 Thread Michael S. Tsirkin
nightly? > > Regards, > - Sedat - > > [1] http://lists.freedesktop.org/archives/intel-gfx/2013-August/032154.html Same thing observed with v3.11-rc7. > > -- Forwarded message -- > From: Sedat Dilek > Date: Tue, Jul 2, 2013 at 7:31 AM > Subject: Re: linux-

Re: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]

2013-07-01 Thread Sedat Dilek
On Mon, Jul 1, 2013 at 11:03 AM, Sedat Dilek wrote: > On Mon, Jul 1, 2013 at 10:52 AM, Daniel Vetter wrote: >> On Mon, Jul 1, 2013 at 10:49 AM, Sedat Dilek wrote: >>> On Mon, Jul 1, 2013 at 9:59 AM, Stephen Rothwell >>> wrote: Hi all, Changes since 20130628: The regula

Re: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]

2013-07-01 Thread Sedat Dilek
On Mon, Jul 1, 2013 at 10:52 AM, Daniel Vetter wrote: > On Mon, Jul 1, 2013 at 10:49 AM, Sedat Dilek wrote: >> On Mon, Jul 1, 2013 at 9:59 AM, Stephen Rothwell >> wrote: >>> Hi all, >>> >>> Changes since 20130628: >>> >>> The regulator tree gained a build failure so I used the version from >>>

Re: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]

2013-07-01 Thread Daniel Vetter
On Mon, Jul 1, 2013 at 10:49 AM, Sedat Dilek wrote: > On Mon, Jul 1, 2013 at 9:59 AM, Stephen Rothwell > wrote: >> Hi all, >> >> Changes since 20130628: >> >> The regulator tree gained a build failure so I used the version from >> next-20130628. >> >> The trivial tree gained a conflict against t