linux-next: Tree for Dec 10

Hi all, Changes since 20201209: The microblaze tree gained a conflict against the asm-generic tree. The pm tree gained a build failure when building htmldocs. The net-next tree gained a conflict against the netfilter tree. The nand tree still had its build failure so I used the version from

linux-next: Tree for Dec 10

Hi all, Changes since 20181207: The thermal tree lost its build failure. The rdma tree still had its build failure so I used the version from next-20181203. The net-next tree gained conflicts against the net tree. The drm-msm tree gained a conflict against the drm tree. The rcu tree gained a

linux-next: Tree for Dec 10

Hi all, Changes since 20151209: I applied a fix patch to the orangefs tree for a build failure exposed by the vfs tree. The vfs tree gained a build failure for which I applied a merge fix patch. The pm tree lost its build failure. The akpm-current tree gained a conflict against the net-next

linux-next: Tree for Dec 10

Hi all, Changes since 20151209: I applied a fix patch to the orangefs tree for a build failure exposed by the vfs tree. The vfs tree gained a build failure for which I applied a merge fix patch. The pm tree lost its build failure. The akpm-current tree gained a conflict against the net-next

Re: linux-next: Tree for Dec 10

Stephen, On Thu, Dec 11, 2014 at 07:51:42AM +1100, Stephen Rothwell wrote: > Hi Jeremiah, > > On Wed, 10 Dec 2014 03:30:14 -0800 Jeremiah Mahler wrote: > > > > Just a FYI. > > > > As of -next 20141210 commit d32394fae95741d733b174ec1446f27765f80233, > > which caused a suspend hang bug [1], is

Re: linux-next: Tree for Dec 10

On Thu, Dec 11, 2014 at 07:51:42AM +1100, Stephen Rothwell wrote: > Hi Jeremiah, > > On Wed, 10 Dec 2014 03:30:14 -0800 Jeremiah Mahler wrote: > > > > Just a FYI. > > > > As of -next 20141210 commit d32394fae95741d733b174ec1446f27765f80233, > > which caused a suspend hang bug [1], is still in

Re: linux-next: Tree for Dec 10

Hi Jeremiah, On Wed, 10 Dec 2014 03:30:14 -0800 Jeremiah Mahler wrote: > > Just a FYI. > > As of -next 20141210 commit d32394fae95741d733b174ec1446f27765f80233, > which caused a suspend hang bug [1], is still in the tree. Greg created > a revert patch for it in driver-core [2] but I am not

Re: linux-next: Tree for Dec 10

Stephen, On Wed, Dec 10, 2014 at 08:48:22PM +1100, Stephen Rothwell wrote: > Hi all, > > Please do not add stuff destined for v3.20 until after v3.19-rc1 is > released. > > Changes since 20141209: > > Dropped tree: access_once > > The thermal tree lost its build failure. > Just a FYI. As

linux-next: Tree for Dec 10

Hi all, Please do not add stuff destined for v3.20 until after v3.19-rc1 is released. Changes since 20141209: Dropped tree: access_once The thermal tree lost its build failure. The net-next tree gained a conflict against the net tree and a build failure for which I applied a patch. The

linux-next: Tree for Dec 10

Hi all, Please do not add stuff destined for v3.20 until after v3.19-rc1 is released. Changes since 20141209: Dropped tree: access_once The thermal tree lost its build failure. The net-next tree gained a conflict against the net tree and a build failure for which I applied a patch. The

Re: linux-next: Tree for Dec 10

Stephen, On Wed, Dec 10, 2014 at 08:48:22PM +1100, Stephen Rothwell wrote: Hi all, Please do not add stuff destined for v3.20 until after v3.19-rc1 is released. Changes since 20141209: Dropped tree: access_once The thermal tree lost its build failure. Just a FYI. As of -next

Re: linux-next: Tree for Dec 10

Hi Jeremiah, On Wed, 10 Dec 2014 03:30:14 -0800 Jeremiah Mahler jmmah...@gmail.com wrote: Just a FYI. As of -next 20141210 commit d32394fae95741d733b174ec1446f27765f80233, which caused a suspend hang bug [1], is still in the tree. Greg created a revert patch for it in driver-core [2] but

Re: linux-next: Tree for Dec 10

On Thu, Dec 11, 2014 at 07:51:42AM +1100, Stephen Rothwell wrote: Hi Jeremiah, On Wed, 10 Dec 2014 03:30:14 -0800 Jeremiah Mahler jmmah...@gmail.com wrote: Just a FYI. As of -next 20141210 commit d32394fae95741d733b174ec1446f27765f80233, which caused a suspend hang bug [1], is still

Re: linux-next: Tree for Dec 10

Stephen, On Thu, Dec 11, 2014 at 07:51:42AM +1100, Stephen Rothwell wrote: Hi Jeremiah, On Wed, 10 Dec 2014 03:30:14 -0800 Jeremiah Mahler jmmah...@gmail.com wrote: Just a FYI. As of -next 20141210 commit d32394fae95741d733b174ec1446f27765f80233, which caused a suspend hang bug

linux-next: Tree for Dec 10

Hi all, Changes since 20131209: The powerpc tree still had its build failure for which I applied a supplied patch. The crypto tree lost its build failure. The sound-asoc tree gained a build failure for which I reverted a commit. The usb-gadget tree gained a build failure so I used the version

linux-next: Tree for Dec 10

Hi all, Changes since 20131209: The powerpc tree still had its build failure for which I applied a supplied patch. The crypto tree lost its build failure. The sound-asoc tree gained a build failure for which I reverted a commit. The usb-gadget tree gained a build failure so I used the version