linux-next: Tree for Mar 14

2016-03-15 Thread Sergey Senozhatsky
On (03/15/16 07:43), Wolfram Sang wrote:
> > Hello,
> > 
> > I'm seeing a bunch of warnings and errors
> 
> I pushed the fix to my for-next branch yesterday. Sorry for the fuzz!

no prob, thanks!

-ss


linux-next: Tree for Mar 14

2016-03-15 Thread Sergey Senozhatsky
On (03/14/16 17:40), Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20160311:
> 
> The vfs tree gained a conflict against Linus' tree. I also applied a
> patch for a known runtime bug.
> 
> The tip tree gained a conflict against the mips tree.
> 
> The aio tree still had a build failure so I removed several commits
> from it.  It also gained a conflict against the vfs tree.
> 
> Non-merge commits (relative to Linus' tree): 11202
>  8646 files changed, 426680 insertions(+), 211740 deletions(-)


Hello,

I'm seeing a bunch of warnings and errors

[0.697413] [ cut here ]
[0.697484] WARNING: CPU: 0 PID: 1 at drivers/i2c/i2c-core.c:1533 
i2c_register_adapter+0x37/0x367
[0.697560] Modules linked in:
[0.697654] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW   
4.5.0-rc7-next-20160314-dbg-00015-gd1f304e-dirty #271
[0.697817]   8801330cf9e8 8124795a 

[0.698029]   8801330cfa28 810444e4 
05fd330cf8d8
[0.698239]  8800bf4b50a8  fff5 
81426c47
[0.698449] Call Trace:
[0.698505]  [] dump_stack+0x67/0x90
[0.698565]  [] __warn+0xc2/0xdd
[0.698623]  [] ? i2c_register_adapter+0x367/0x367
[0.698683]  [] warn_slowpath_null+0x1d/0x1f
[0.698743]  [] i2c_register_adapter+0x37/0x367
[0.698803]  [] ? i2c_register_adapter+0x367/0x367
[0.698863]  [] i2c_add_adapter+0x60/0x65
[0.698922]  [] __i2c_bit_add_bus+0x294/0x2f3
[0.698981]  [] i2c_bit_add_bus+0x15/0x17
[0.699041]  [] nvkm_i2c_bus_ctor+0x1bb/0x1dd
[0.699100]  [] nv50_i2c_bus_new+0xa6/0xd0
[0.699160]  [] nvkm_i2c_new_+0x220/0x57c
[0.699219]  [] ? nvkm_gpio_new_+0x7b/0x86
[0.699278]  [] g94_i2c_new+0x1d/0x1f
[0.699337]  [] nvkm_device_ctor+0x100e/0x2211
[0.699397]  [] nvkm_device_pci_new+0x18c/0x19f
[0.699457]  [] nouveau_drm_probe+0x194/0x1d7
[0.699517]  [] pci_device_probe+0x85/0xee
[0.699578]  [] driver_probe_device+0x118/0x261
[0.699638]  [] __driver_attach+0x73/0x95
[0.699697]  [] ? driver_probe_device+0x261/0x261
[0.699757]  [] bus_for_each_dev+0x6f/0x87
[0.699815]  [] driver_attach+0x1e/0x20
[0.699874]  [] bus_add_driver+0xf2/0x1e4
[0.699932]  [] driver_register+0x8a/0xc6
[0.61]  [] __pci_register_driver+0x60/0x63
[0.700052]  [] drm_pci_init+0x50/0xd1
[0.700110]  [] ? ttm_init+0x60/0x60
[0.700168]  [] nouveau_drm_init+0x1f4/0x1f6
[0.700229]  [] do_one_initcall+0xe7/0x16c
[0.700290]  [] kernel_init_freeable+0x118/0x19e
[0.700351]  [] kernel_init+0xe/0xf0
[0.700409]  [] ret_from_fork+0x22/0x40
[0.700513]  [] ? rest_init+0x136/0x136
[0.700581] ---[ end trace e54473700ba2f16a ]---
[0.700643] [ cut here ]
[0.700701] WARNING: CPU: 0 PID: 1 at drivers/i2c/i2c-core.c:1533 
i2c_register_adapter+0x37/0x367
[0.700777] Modules linked in:
[0.700869] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW   
4.5.0-rc7-next-20160314-dbg-00015-gd1f304e-dirty #271
[0.701031]   8801330cf9e8 8124795a 

[0.701243]   8801330cfa28 810444e4 
05fd330cfa78
[0.701455]  8800bf4b58a8  fff5 
81426c47
[0.701667] Call Trace:
[0.701721]  [] dump_stack+0x67/0x90
[0.701779]  [] __warn+0xc2/0xdd
[0.701837]  [] ? i2c_register_adapter+0x367/0x367
[0.701897]  [] warn_slowpath_null+0x1d/0x1f
[0.701956]  [] i2c_register_adapter+0x37/0x367
[0.705165]  [] ? i2c_register_adapter+0x367/0x367
[0.705225]  [] i2c_add_adapter+0x60/0x65
[0.705284]  [] __i2c_bit_add_bus+0x294/0x2f3
[0.705343]  [] i2c_bit_add_bus+0x15/0x17
[0.705402]  [] nvkm_i2c_bus_ctor+0x1bb/0x1dd
[0.705461]  [] nv50_i2c_bus_new+0xa6/0xd0
[0.705520]  [] nvkm_i2c_new_+0x220/0x57c
[0.705580]  [] ? nvkm_gpio_new_+0x7b/0x86
[0.705639]  [] g94_i2c_new+0x1d/0x1f
[0.705698]  [] nvkm_device_ctor+0x100e/0x2211
[0.705757]  [] nvkm_device_pci_new+0x18c/0x19f
[0.705817]  [] nouveau_drm_probe+0x194/0x1d7
[0.705876]  [] pci_device_probe+0x85/0xee
[0.705935]  [] driver_probe_device+0x118/0x261
[0.705995]  [] __driver_attach+0x73/0x95
[0.706053]  [] ? driver_probe_device+0x261/0x261
[0.706113]  [] bus_for_each_dev+0x6f/0x87
[0.706172]  [] driver_attach+0x1e/0x20
[0.706230]  [] bus_add_driver+0xf2/0x1e4
[0.706289]  [] driver_register+0x8a/0xc6
[0.706347]  [] __pci_register_driver+0x60/0x63
[0.706407]  [] drm_pci_init+0x50/0xd1
[0.706486]  [] ? ttm_init+0x60/0x60
[0.706544]  [] nouveau_drm_init+0x1f4/0x1f6
[0.706603]  [] do_one_initcall+0xe7/0x16c
[0.706663]  [] kernel_init_freeable+0x118/0x19e
[0.706722]  [] kernel_init+0xe/0xf0
[0.706780]  [] ret_from_fork+0x22/0x40
[0.706838]  [] ? rest_init+0x136/0x136
[0.706906] ---[ end trace 

linux-next: Tree for Mar 14

2016-03-15 Thread Wolfram Sang
On Tue, Mar 15, 2016 at 09:30:29AM +0900, Sergey Senozhatsky wrote:
> On (03/14/16 17:40), Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20160311:
> > 
> > The vfs tree gained a conflict against Linus' tree. I also applied a
> > patch for a known runtime bug.
> > 
> > The tip tree gained a conflict against the mips tree.
> > 
> > The aio tree still had a build failure so I removed several commits
> > from it.  It also gained a conflict against the vfs tree.
> > 
> > Non-merge commits (relative to Linus' tree): 11202
> >  8646 files changed, 426680 insertions(+), 211740 deletions(-)
> 
> 
> Hello,
> 
> I'm seeing a bunch of warnings and errors

I pushed the fix to my for-next branch yesterday. Sorry for the fuzz!

-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: