Hi all,
News: The merge window has opened, so please do not add any v5.10
related material to your linux-next included branches until after the
merge window closes again.
Changes since 20200810:
Dropped tree: set_fs at maintainer's request
My fixes tree contains:
73c7adb54169 ("device_cgr
Hi all,
Changes since 20170810:
New tree: clk-samsung
The pm tree gained a conflict against the tty.current tree.
The tip tree gained a conflict against the pm tree.
The rcu tree gained a build failure due to an interaction with the tip
tree for which I applied a temporary hack.
I again rever
Hi all,
Changes since 20160809:
Non-merge commits (relative to Linus' tree): 1334
1380 files changed, 35797 insertions(+), 12995 deletions(-)
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linu
On 08/11/2014 05:59 PM, Stephen Rothwell wrote:
Hi Guenter,
On Mon, 11 Aug 2014 10:05:10 -0700 Guenter Roeck wrote:
New build failures:
Building arm:s5pv210_defconfig ... failed
--
Error log:
arch/arm/mach-s5pv210/pm.c:150:12: error: 'suspend_valid_only_mem' undeclared
here (not
Hi Guenter,
On Mon, 11 Aug 2014 10:05:10 -0700 Guenter Roeck wrote:
>
> New build failures:
>
> Building arm:s5pv210_defconfig ... failed
> --
> Error log:
> arch/arm/mach-s5pv210/pm.c:150:12: error: 'suspend_valid_only_mem' undeclared
> here (not in a function)
> make[1]: *** [arch/
From: Jeff Kirsher
Date: Mon, 11 Aug 2014 15:16:32 -0700
> On Mon, 2014-08-11 at 14:54 -0700, David Miller wrote:
>> I see no such change in my tree.
>
> http://patchwork.ozlabs.org/patch/376699/
>
> This is what I was referring to, it looks like you set the patch status
> to "Awaiting upstream
On Mon, 2014-08-11 at 14:54 -0700, David Miller wrote:
> From: Jeff Kirsher
> Date: Mon, 11 Aug 2014 12:53:06 -0700
>
> > On Mon, 2014-08-11 at 09:17 -0700, Randy Dunlap wrote:
> >> On 08/10/14 22:52, Stephen Rothwell wrote:
> >> > Hi all,
> >> >
> >> > Please do not add code intended for v3.18
From: Jeff Kirsher
Date: Mon, 11 Aug 2014 12:53:06 -0700
> On Mon, 2014-08-11 at 09:17 -0700, Randy Dunlap wrote:
>> On 08/10/14 22:52, Stephen Rothwell wrote:
>> > Hi all,
>> >
>> > Please do not add code intended for v3.18 until after v3.17-rc1 is
>> > released.
>> >
>> > Changes since 201408
On Mon, 2014-08-11 at 09:17 -0700, Randy Dunlap wrote:
> On 08/10/14 22:52, Stephen Rothwell wrote:
> > Hi all,
> >
> > Please do not add code intended for v3.18 until after v3.17-rc1 is
> > released.
> >
> > Changes since 20140808:
> >
>
> on i386 and x86_64:
>
> ../drivers/net/ethernet/intel
On Mon, Aug 11, 2014 at 03:52:13PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add code intended for v3.18 until after v3.17-rc1 is
> released.
>
> Changes since 20140808:
>
> The ext3 tree lost its build failure.
>
> The pm tree gained conflicts against Linus' tree and a build f
On 08/10/14 22:52, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add code intended for v3.18 until after v3.17-rc1 is
> released.
>
> Changes since 20140808:
>
on i386 and x86_64:
../drivers/net/ethernet/intel/i40e/i40e_fcoe.c: In function
'i40e_get_fcoe_tc_map':
../drivers/net/ethernet
Hi all,
Please do not add code intended for v3.18 until after v3.17-rc1 is
released.
Changes since 20140808:
The ext3 tree lost its build failure.
The pm tree gained conflicts against Linus' tree and a build failure for
which I applied a merge fix patch.
The mmc-uh tree still had its build fai
12 matches
Mail list logo