linux-next: Tree for Apr 26

2019-04-26 Thread Stephen Rothwell
Hi all, Changes since 20190424: The rdma-fixes tree gained a conflict against Linus' tree. The qcom tree lost its build failure. The next-next tree lost its build failure. The ipsec-next tree gained a conflict against the ipsec tree. The drm tree gained a build failure due to a bad automatic

linux-next: Tree for Apr 26

2018-04-25 Thread Stephen Rothwell
Hi all, News: There will be no linux-next release tomorrow. Changes since 20180424: The qcom tree gained a build failure so I used the version from next-20180424. The clk-samsung tree gained a build failure so I used the version from next-20180424. The bpf-next tree gained conflicts against

linux-next: Tree for Apr 26

2018-04-25 Thread Stephen Rothwell
Hi all, News: There will be no linux-next release tomorrow. Changes since 20180424: The qcom tree gained a build failure so I used the version from next-20180424. The clk-samsung tree gained a build failure so I used the version from next-20180424. The bpf-next tree gained conflicts against

Re: linux-next: Tree for Apr 26 (net/can/bcm.c)

2017-04-26 Thread Oliver Hartkopp
Hi Randy, thanks for the report! Some fallout of my namespace support integration %-) I posted a patch for it: http://marc.info/?l=linux-can=149323049630039=2 Many thanks & best regards, Oliver On 04/26/2017 04:53 PM, Randy Dunlap wrote: On 04/26/17 01:03, Stephen Rothwell wrote: Hi all,

Re: linux-next: Tree for Apr 26 (net/can/bcm.c)

2017-04-26 Thread Oliver Hartkopp
Hi Randy, thanks for the report! Some fallout of my namespace support integration %-) I posted a patch for it: http://marc.info/?l=linux-can=149323049630039=2 Many thanks & best regards, Oliver On 04/26/2017 04:53 PM, Randy Dunlap wrote: On 04/26/17 01:03, Stephen Rothwell wrote: Hi all,

Re: linux-next: Tree for Apr 26 (net/can/bcm.c)

2017-04-26 Thread Randy Dunlap
On 04/26/17 01:03, Stephen Rothwell wrote: > Hi all, > > Changes since 20170424: > on x86_64: when CONFIG_PROC_FS is not enabled: ../net/can/bcm.c:1541:14: error: 'struct netns_can' has no member named 'bcmproc_dir' ../net/can/bcm.c:1601:14: error: 'struct netns_can' has no member named

Re: linux-next: Tree for Apr 26 (net/can/bcm.c)

2017-04-26 Thread Randy Dunlap
On 04/26/17 01:03, Stephen Rothwell wrote: > Hi all, > > Changes since 20170424: > on x86_64: when CONFIG_PROC_FS is not enabled: ../net/can/bcm.c:1541:14: error: 'struct netns_can' has no member named 'bcmproc_dir' ../net/can/bcm.c:1601:14: error: 'struct netns_can' has no member named

linux-next: Tree for Apr 26

2017-04-26 Thread Stephen Rothwell
Hi all, Changes since 20170424: The net-next tree gained a conflict against the kbuild tree. The tip tree lost its build failure and gained a conflict against the powerpc tree. The scsi-mkp tree gained a conflict against the block tree. The nvdimm tree lost its build failure. Non-merge

linux-next: Tree for Apr 26

2017-04-26 Thread Stephen Rothwell
Hi all, Changes since 20170424: The net-next tree gained a conflict against the kbuild tree. The tip tree lost its build failure and gained a conflict against the powerpc tree. The scsi-mkp tree gained a conflict against the block tree. The nvdimm tree lost its build failure. Non-merge

linux-next: Tree for Apr 26

2016-04-26 Thread Stephen Rothwell
Hi all, Changes since 20160422: New tree: kbuild-pitre The arm-soc tree gained a build failure so I used the version from next-20160422. The pci tree lost its build failure but gained another for which I applied a merg fix patch. The pm tree gained a conflict against the renesas tree. The

linux-next: Tree for Apr 26

2016-04-26 Thread Stephen Rothwell
Hi all, Changes since 20160422: New tree: kbuild-pitre The arm-soc tree gained a build failure so I used the version from next-20160422. The pci tree lost its build failure but gained another for which I applied a merg fix patch. The pm tree gained a conflict against the renesas tree. The

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-07-11 Thread Sedat Dilek
On Wed, Jul 10, 2013 at 7:30 PM, Gustavo Padovan wrote: > Hi Sedat, > > * Sedat Dilek [2013-04-26 19:40:20 +0200]: > >> On Fri, Apr 26, 2013 at 7:32 PM, Sedat Dilek wrote: >> > On Fri, Apr 26, 2013 at 7:30 PM, Sedat Dilek wrote: >> >> On Fri, Apr 26, 2013 at 10:03 AM, Stephen Rothwell >> >>

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-07-11 Thread Sedat Dilek
On Wed, Jul 10, 2013 at 7:30 PM, Gustavo Padovan gust...@padovan.org wrote: Hi Sedat, * Sedat Dilek sedat.di...@gmail.com [2013-04-26 19:40:20 +0200]: On Fri, Apr 26, 2013 at 7:32 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 26, 2013 at 7:30 PM, Sedat Dilek sedat.di...@gmail.com

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-07-10 Thread Gustavo Padovan
Hi Sedat, * Sedat Dilek [2013-04-26 19:40:20 +0200]: > On Fri, Apr 26, 2013 at 7:32 PM, Sedat Dilek wrote: > > On Fri, Apr 26, 2013 at 7:30 PM, Sedat Dilek wrote: > >> On Fri, Apr 26, 2013 at 10:03 AM, Stephen Rothwell > >> wrote: > >>> Hi all, > >>> > >>> Changes since 20130424: > >>> >

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-07-10 Thread Gustavo Padovan
Hi Sedat, * Sedat Dilek sedat.di...@gmail.com [2013-04-26 19:40:20 +0200]: On Fri, Apr 26, 2013 at 7:32 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 26, 2013 at 7:30 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 26, 2013 at 10:03 AM, Stephen Rothwell

Re: linux-next: Tree for Apr 26

2013-04-29 Thread Matt Fleming
On 29/04/13 09:53, Stephen Rothwell wrote: > On Mon, 29 Apr 2013 09:11:13 +0100 Matt Fleming > wrote: >> >> On 29/04/13 00:36, Stephen Rothwell wrote: >>> Commit e29c2de5f591 ("Merge tag 'v3.9-rc8' into efi-for-tip") by Matt >>> Fleming from the tip tree merged v3.9-rc8 (which has 0635eb8a54cf)

Re: linux-next: Tree for Apr 26

2013-04-29 Thread Stephen Rothwell
On Mon, 29 Apr 2013 09:11:13 +0100 Matt Fleming wrote: > > On 29/04/13 00:36, Stephen Rothwell wrote: > > Commit e29c2de5f591 ("Merge tag 'v3.9-rc8' into efi-for-tip") by Matt > > Fleming from the tip tree merged v3.9-rc8 (which has 0635eb8a54cf) with > > the branch that contains 048517722cde but

Re: linux-next: Tree for Apr 26

2013-04-29 Thread Matt Fleming
On 29/04/13 00:36, Stephen Rothwell wrote: > Commit e29c2de5f591 ("Merge tag 'v3.9-rc8' into efi-for-tip") by Matt > Fleming from the tip tree merged v3.9-rc8 (which has 0635eb8a54cf) with > the branch that contains 048517722cde but lost the "select UCS2_STRING" > which should be in

Re: linux-next: Tree for Apr 26

2013-04-29 Thread Sedat Dilek
On Mon, Apr 29, 2013 at 8:58 AM, Geert Uytterhoeven wrote: > On Mon, Apr 29, 2013 at 1:36 AM, Stephen Rothwell > wrote: >> P.S. Geert, please trim your replies. > > Sorry, I noticed only after sending. > (First time I wanted to reply without quoting anything using the new gmail > web interface.

Re: linux-next: Tree for Apr 26

2013-04-29 Thread Geert Uytterhoeven
On Mon, Apr 29, 2013 at 1:36 AM, Stephen Rothwell wrote: > P.S. Geert, please trim your replies. Sorry, I noticed only after sending. (First time I wanted to reply without quoting anything using the new gmail web interface. So it was not intuitive ;-) Gr{oetje,eeting}s,

Re: linux-next: Tree for Apr 26

2013-04-29 Thread Geert Uytterhoeven
On Mon, Apr 29, 2013 at 1:36 AM, Stephen Rothwell s...@canb.auug.org.au wrote: P.S. Geert, please trim your replies. Sorry, I noticed only after sending. (First time I wanted to reply without quoting anything using the new gmail web interface. So it was not intuitive ;-) Gr{oetje,eeting}s,

Re: linux-next: Tree for Apr 26

2013-04-29 Thread Sedat Dilek
On Mon, Apr 29, 2013 at 8:58 AM, Geert Uytterhoeven ge...@linux-m68k.org wrote: On Mon, Apr 29, 2013 at 1:36 AM, Stephen Rothwell s...@canb.auug.org.au wrote: P.S. Geert, please trim your replies. Sorry, I noticed only after sending. (First time I wanted to reply without quoting anything

Re: linux-next: Tree for Apr 26

2013-04-29 Thread Matt Fleming
On 29/04/13 00:36, Stephen Rothwell wrote: Commit e29c2de5f591 (Merge tag 'v3.9-rc8' into efi-for-tip) by Matt Fleming from the tip tree merged v3.9-rc8 (which has 0635eb8a54cf) with the branch that contains 048517722cde but lost the select UCS2_STRING which should be in

Re: linux-next: Tree for Apr 26

2013-04-29 Thread Stephen Rothwell
On Mon, 29 Apr 2013 09:11:13 +0100 Matt Fleming matt.flem...@intel.com wrote: On 29/04/13 00:36, Stephen Rothwell wrote: Commit e29c2de5f591 (Merge tag 'v3.9-rc8' into efi-for-tip) by Matt Fleming from the tip tree merged v3.9-rc8 (which has 0635eb8a54cf) with the branch that contains

Re: linux-next: Tree for Apr 26

2013-04-29 Thread Matt Fleming
On 29/04/13 09:53, Stephen Rothwell wrote: On Mon, 29 Apr 2013 09:11:13 +0100 Matt Fleming matt.flem...@intel.com wrote: On 29/04/13 00:36, Stephen Rothwell wrote: Commit e29c2de5f591 (Merge tag 'v3.9-rc8' into efi-for-tip) by Matt Fleming from the tip tree merged v3.9-rc8 (which has

Re: linux-next: Tree for Apr 26

2013-04-28 Thread Stephen Rothwell
Hi all, On Sat, 27 Apr 2013 19:06:53 +0200 Geert Uytterhoeven wrote: > > ia64-defconfig: > > (.text+0x3956a2): undefined reference to `ucs2_strsize' > (.text+0x395f82): undefined reference to `ucs2_strsize' > (.text+0x395fa2): undefined reference to `ucs2_strsize' > (.text+0x396222): undefined

Re: linux-next: Tree for Apr 26

2013-04-28 Thread Stephen Rothwell
Hi all, On Sat, 27 Apr 2013 19:06:53 +0200 Geert Uytterhoeven ge...@linux-m68k.org wrote: ia64-defconfig: (.text+0x3956a2): undefined reference to `ucs2_strsize' (.text+0x395f82): undefined reference to `ucs2_strsize' (.text+0x395fa2): undefined reference to `ucs2_strsize'

Re: linux-next: Tree for Apr 26

2013-04-27 Thread Yann E. MORIN
Sedat, All, On Sat, Apr 27, 2013 at 01:30:33PM +0200, Sedat Dilek wrote: > On Sat, Apr 27, 2013 at 8:54 AM, Michal Marek wrote: > > That (silent)oldconfig with stdin redirection throws an error if it > > encounters a new option is expected and correct. The bug here is that > > _normal_ oldconfig

Re: linux-next: Tree for Apr 26

2013-04-27 Thread Yann E. MORIN
Michal, All, On Sat, Apr 27, 2013 at 08:54:37AM +0200, Michal Marek wrote: > That (silent)oldconfig with stdin redirection throws an error if it > encounters a new option is expected and correct. The bug here is that > _normal_ oldconfig run apparently does not set all the options. I.e. > > $

Re: linux-next: Tree for Apr 26

2013-04-27 Thread Sedat Dilek
On Sat, Apr 27, 2013 at 8:54 AM, Michal Marek wrote: > Dne 27.4.2013 00:01, Yann E. MORIN napsal(a): >> Michal, Sedat, All, >> >> On Fri, Apr 26, 2013 at 01:13:33PM +0200, Michal Marek wrote: >>> On 26.4.2013 13:08, Michal Marek wrote: On 26.4.2013 12:49, Sedat Dilek wrote: > With

Re: linux-next: Tree for Apr 26

2013-04-27 Thread Michal Marek
Dne 27.4.2013 00:01, Yann E. MORIN napsal(a): > Michal, Sedat, All, > > On Fri, Apr 26, 2013 at 01:13:33PM +0200, Michal Marek wrote: >> On 26.4.2013 13:08, Michal Marek wrote: >>> On 26.4.2013 12:49, Sedat Dilek wrote: With reverting all kbuild-next commits I was able to build again.

Re: linux-next: Tree for Apr 26

2013-04-27 Thread Michal Marek
Dne 27.4.2013 00:01, Yann E. MORIN napsal(a): Michal, Sedat, All, On Fri, Apr 26, 2013 at 01:13:33PM +0200, Michal Marek wrote: On 26.4.2013 13:08, Michal Marek wrote: On 26.4.2013 12:49, Sedat Dilek wrote: With reverting all kbuild-next commits I was able to build again. Revert

Re: linux-next: Tree for Apr 26

2013-04-27 Thread Sedat Dilek
On Sat, Apr 27, 2013 at 8:54 AM, Michal Marek mma...@suse.cz wrote: Dne 27.4.2013 00:01, Yann E. MORIN napsal(a): Michal, Sedat, All, On Fri, Apr 26, 2013 at 01:13:33PM +0200, Michal Marek wrote: On 26.4.2013 13:08, Michal Marek wrote: On 26.4.2013 12:49, Sedat Dilek wrote: With reverting

Re: linux-next: Tree for Apr 26

2013-04-27 Thread Yann E. MORIN
Michal, All, On Sat, Apr 27, 2013 at 08:54:37AM +0200, Michal Marek wrote: That (silent)oldconfig with stdin redirection throws an error if it encounters a new option is expected and correct. The bug here is that _normal_ oldconfig run apparently does not set all the options. I.e. $ yes |

Re: linux-next: Tree for Apr 26

2013-04-27 Thread Yann E. MORIN
Sedat, All, On Sat, Apr 27, 2013 at 01:30:33PM +0200, Sedat Dilek wrote: On Sat, Apr 27, 2013 at 8:54 AM, Michal Marek mma...@suse.cz wrote: That (silent)oldconfig with stdin redirection throws an error if it encounters a new option is expected and correct. The bug here is that _normal_

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-04-26 Thread Sedat Dilek
On Sat, Apr 27, 2013 at 12:04 AM, Tejun Heo wrote: > On Fri, Apr 26, 2013 at 11:07:44PM +0200, Sedat Dilek wrote: >> > The second argument %rsi is zero, which got transferred to %r13 and >> > then offset deref on it trapped. >> > >> > The second argument is @wq and the oopsing code is the

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-04-26 Thread Tejun Heo
On Fri, Apr 26, 2013 at 11:07:44PM +0200, Sedat Dilek wrote: > > The second argument %rsi is zero, which got transferred to %r13 and > > then offset deref on it trapped. > > > > The second argument is @wq and the oopsing code is the wq->flags deref > > in the following if condition. > > > >

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Yann E. MORIN
Michal, Sedat, All, On Fri, Apr 26, 2013 at 01:13:33PM +0200, Michal Marek wrote: > On 26.4.2013 13:08, Michal Marek wrote: > > On 26.4.2013 12:49, Sedat Dilek wrote: > >> With reverting all kbuild-next commits I was able to build again. > >> > >> Revert "kconfig: implement

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 8:22 PM, Tejun Heo wrote: > On Fri, Apr 26, 2013 at 07:40:20PM +0200, Sedat Dilek wrote: >> Oops, NULL-pointer-deref [ __queue_work() ] >> >> [ 25.974932] BUG: unable to handle kernel NULL pointer dereference >> at 0100 >> [ 25.974944] IP: []

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 8:43 PM, Frederic Weisbecker wrote: > 2013/4/26 Sedat Dilek : >> On Fri, Apr 26, 2013 at 8:22 PM, Tejun Heo wrote: >>> On Fri, Apr 26, 2013 at 07:40:20PM +0200, Sedat Dilek wrote: Oops, NULL-pointer-deref [ __queue_work() ] [ 25.974932] BUG: unable to

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-04-26 Thread Frederic Weisbecker
2013/4/26 Sedat Dilek : > On Fri, Apr 26, 2013 at 8:22 PM, Tejun Heo wrote: >> On Fri, Apr 26, 2013 at 07:40:20PM +0200, Sedat Dilek wrote: >>> Oops, NULL-pointer-deref [ __queue_work() ] >>> >>> [ 25.974932] BUG: unable to handle kernel NULL pointer dereference >>> at 0100 >>> [

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-04-26 Thread Tejun Heo
On Fri, Apr 26, 2013 at 07:40:20PM +0200, Sedat Dilek wrote: > Oops, NULL-pointer-deref [ __queue_work() ] > > [ 25.974932] BUG: unable to handle kernel NULL pointer dereference > at 0100 > [ 25.974944] IP: [] __queue_work+0x32/0x3d0 So, 0x100 deref near the top of the function.

Re: linux-next: Tree for Apr 26 (nfc)

2013-04-26 Thread Marcel Holtmann
Hi Randy, >> Hi all, >> >> Changes since 20130424: >> > > > on i386: > > net/built-in.o: In function `nfc_unregister_device': > (.text+0x6a36d): undefined reference to `rfkill_unregister' > net/built-in.o: In function `nfc_unregister_device': > (.text+0x6a378): undefined reference to

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 7:32 PM, Sedat Dilek wrote: > On Fri, Apr 26, 2013 at 7:30 PM, Sedat Dilek wrote: >> On Fri, Apr 26, 2013 at 10:03 AM, Stephen Rothwell >> wrote: >>> Hi all, >>> >>> Changes since 20130424: >>> >>> Removed tree: ppc-temp (remerged into powerpc) >>> >>> The net-next tree

Re: linux-next: Tree for Apr 26 (nfc)

2013-04-26 Thread Randy Dunlap
On 04/26/13 01:03, Stephen Rothwell wrote: > Hi all, > > Changes since 20130424: > on i386: net/built-in.o: In function `nfc_unregister_device': (.text+0x6a36d): undefined reference to `rfkill_unregister' net/built-in.o: In function `nfc_unregister_device': (.text+0x6a378): undefined

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 10:03 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20130424: > > Removed tree: ppc-temp (remerged into powerpc) > > The net-next tree gained conflicts against the net and pci trees and a > build failure for which I applied a merge fix patch. > > The omap_dss2

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Yann E. MORIN
Michal, Sedat, All, On Fri, Apr 26, 2013 at 01:08:35PM +0200, Michal Marek wrote: > On 26.4.2013 12:49, Sedat Dilek wrote: > > On Fri, Apr 26, 2013 at 12:37 PM, Sedat Dilek wrote: > >> On Fri, Apr 26, 2013 at 12:35 PM, Sedat Dilek > >> wrote: > >>> On Fri, Apr 26, 2013 at 12:04 PM, Michal

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Michal Marek
On 26.4.2013 13:45, Sedat Dilek wrote: > On Fri, Apr 26, 2013 at 1:23 PM, Sedat Dilek wrote: >> On Fri, Apr 26, 2013 at 1:13 PM, Michal Marek wrote: >>> On 26.4.2013 13:08, Michal Marek wrote: On 26.4.2013 12:49, Sedat Dilek wrote: > With reverting all kbuild-next commits I was able to

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 1:23 PM, Sedat Dilek wrote: > On Fri, Apr 26, 2013 at 1:13 PM, Michal Marek wrote: >> On 26.4.2013 13:08, Michal Marek wrote: >>> On 26.4.2013 12:49, Sedat Dilek wrote: With reverting all kbuild-next commits I was able to build again. Revert "kconfig:

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 1:13 PM, Michal Marek wrote: > On 26.4.2013 13:08, Michal Marek wrote: >> On 26.4.2013 12:49, Sedat Dilek wrote: >>> With reverting all kbuild-next commits I was able to build again. >>> >>> Revert "kconfig: implement KCONFIG_PROBABILITY for randconfig" >>>

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Michal Marek
On 26.4.2013 13:08, Michal Marek wrote: > On 26.4.2013 12:49, Sedat Dilek wrote: >> With reverting all kbuild-next commits I was able to build again. >> >> Revert "kconfig: implement KCONFIG_PROBABILITY for randconfig" >> Revert "kconfig: allow specifying the seed for randconfig" >>

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Michal Marek
On 26.4.2013 12:49, Sedat Dilek wrote: > On Fri, Apr 26, 2013 at 12:37 PM, Sedat Dilek wrote: >> On Fri, Apr 26, 2013 at 12:35 PM, Sedat Dilek wrote: >>> On Fri, Apr 26, 2013 at 12:04 PM, Michal Marek wrote: On Fri, Apr 26, 2013 at 11:58:25AM +0200, Michal Marek wrote: > Can you send a

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 12:37 PM, Sedat Dilek wrote: > On Fri, Apr 26, 2013 at 12:35 PM, Sedat Dilek wrote: >> On Fri, Apr 26, 2013 at 12:04 PM, Michal Marek wrote: >>> On Fri, Apr 26, 2013 at 11:58:25AM +0200, Michal Marek wrote: Can you send a copy of your .config? >>> >>> I can

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 12:35 PM, Sedat Dilek wrote: > On Fri, Apr 26, 2013 at 12:04 PM, Michal Marek wrote: >> On Fri, Apr 26, 2013 at 11:58:25AM +0200, Michal Marek wrote: >>> Can you send a copy of your .config? >> >> I can reproduce it as well: >> >> $ yes "" | make oldconfig >> ... >>

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Michal Marek
Added Yann, from whom I merged couple of kconfig changes yesterday. On 26.4.2013 11:42, Sedat Dilek wrote: > [ CC linux-kbuild folks ] > > I am always doing a ... > >$ cd linux-next/ > >$ yes "" | make oldconfig > > ... before starting a kernel-build. > > Today, I see this ... > > $

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 11:42 AM, Sedat Dilek wrote: > On Fri, Apr 26, 2013 at 10:03 AM, Stephen Rothwell > wrote: >> Hi all, >> >> Changes since 20130424: >> >> Removed tree: ppc-temp (remerged into powerpc) >> >> The net-next tree gained conflicts against the net and pci trees and a >> build

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 10:03 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20130424: > > Removed tree: ppc-temp (remerged into powerpc) > > The net-next tree gained conflicts against the net and pci trees and a > build failure for which I applied a merge fix patch. > > The omap_dss2

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 10:03 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, Changes since 20130424: Removed tree: ppc-temp (remerged into powerpc) The net-next tree gained conflicts against the net and pci trees and a build failure for which I applied a merge fix patch. The

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 11:42 AM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 26, 2013 at 10:03 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, Changes since 20130424: Removed tree: ppc-temp (remerged into powerpc) The net-next tree gained conflicts against the net and

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Michal Marek
Added Yann, from whom I merged couple of kconfig changes yesterday. On 26.4.2013 11:42, Sedat Dilek wrote: [ CC linux-kbuild folks ] I am always doing a ... $ cd linux-next/ $ yes | make oldconfig ... before starting a kernel-build. Today, I see this ... $

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 12:35 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 26, 2013 at 12:04 PM, Michal Marek mma...@suse.cz wrote: On Fri, Apr 26, 2013 at 11:58:25AM +0200, Michal Marek wrote: Can you send a copy of your .config? I can reproduce it as well: $ yes | make

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 12:37 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 26, 2013 at 12:35 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 26, 2013 at 12:04 PM, Michal Marek mma...@suse.cz wrote: On Fri, Apr 26, 2013 at 11:58:25AM +0200, Michal Marek wrote: Can you send

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Michal Marek
On 26.4.2013 12:49, Sedat Dilek wrote: On Fri, Apr 26, 2013 at 12:37 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 26, 2013 at 12:35 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 26, 2013 at 12:04 PM, Michal Marek mma...@suse.cz wrote: On Fri, Apr 26, 2013 at 11:58:25AM

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Michal Marek
On 26.4.2013 13:08, Michal Marek wrote: On 26.4.2013 12:49, Sedat Dilek wrote: With reverting all kbuild-next commits I was able to build again. Revert kconfig: implement KCONFIG_PROBABILITY for randconfig Revert kconfig: allow specifying the seed for randconfig Revert

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 1:13 PM, Michal Marek mma...@suse.cz wrote: On 26.4.2013 13:08, Michal Marek wrote: On 26.4.2013 12:49, Sedat Dilek wrote: With reverting all kbuild-next commits I was able to build again. Revert kconfig: implement KCONFIG_PROBABILITY for randconfig Revert

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 1:23 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 26, 2013 at 1:13 PM, Michal Marek mma...@suse.cz wrote: On 26.4.2013 13:08, Michal Marek wrote: On 26.4.2013 12:49, Sedat Dilek wrote: With reverting all kbuild-next commits I was able to build again.

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Michal Marek
On 26.4.2013 13:45, Sedat Dilek wrote: On Fri, Apr 26, 2013 at 1:23 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 26, 2013 at 1:13 PM, Michal Marek mma...@suse.cz wrote: On 26.4.2013 13:08, Michal Marek wrote: On 26.4.2013 12:49, Sedat Dilek wrote: With reverting all kbuild-next

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Yann E. MORIN
Michal, Sedat, All, On Fri, Apr 26, 2013 at 01:08:35PM +0200, Michal Marek wrote: On 26.4.2013 12:49, Sedat Dilek wrote: On Fri, Apr 26, 2013 at 12:37 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 26, 2013 at 12:35 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 26,

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 10:03 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, Changes since 20130424: Removed tree: ppc-temp (remerged into powerpc) The net-next tree gained conflicts against the net and pci trees and a build failure for which I applied a merge fix patch. The

Re: linux-next: Tree for Apr 26 (nfc)

2013-04-26 Thread Randy Dunlap
On 04/26/13 01:03, Stephen Rothwell wrote: Hi all, Changes since 20130424: on i386: net/built-in.o: In function `nfc_unregister_device': (.text+0x6a36d): undefined reference to `rfkill_unregister' net/built-in.o: In function `nfc_unregister_device': (.text+0x6a378): undefined reference to

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 7:32 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 26, 2013 at 7:30 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 26, 2013 at 10:03 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, Changes since 20130424: Removed tree: ppc-temp

Re: linux-next: Tree for Apr 26 (nfc)

2013-04-26 Thread Marcel Holtmann
Hi Randy, Hi all, Changes since 20130424: on i386: net/built-in.o: In function `nfc_unregister_device': (.text+0x6a36d): undefined reference to `rfkill_unregister' net/built-in.o: In function `nfc_unregister_device': (.text+0x6a378): undefined reference to `rfkill_destroy'

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-04-26 Thread Tejun Heo
On Fri, Apr 26, 2013 at 07:40:20PM +0200, Sedat Dilek wrote: Oops, NULL-pointer-deref [ __queue_work() ] [ 25.974932] BUG: unable to handle kernel NULL pointer dereference at 0100 [ 25.974944] IP: [81077502] __queue_work+0x32/0x3d0 So, 0x100 deref near the top of the

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-04-26 Thread Frederic Weisbecker
2013/4/26 Sedat Dilek sedat.di...@gmail.com: On Fri, Apr 26, 2013 at 8:22 PM, Tejun Heo t...@kernel.org wrote: On Fri, Apr 26, 2013 at 07:40:20PM +0200, Sedat Dilek wrote: Oops, NULL-pointer-deref [ __queue_work() ] [ 25.974932] BUG: unable to handle kernel NULL pointer dereference at

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 8:43 PM, Frederic Weisbecker fweis...@gmail.com wrote: 2013/4/26 Sedat Dilek sedat.di...@gmail.com: On Fri, Apr 26, 2013 at 8:22 PM, Tejun Heo t...@kernel.org wrote: On Fri, Apr 26, 2013 at 07:40:20PM +0200, Sedat Dilek wrote: Oops, NULL-pointer-deref [ __queue_work() ]

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-04-26 Thread Sedat Dilek
On Fri, Apr 26, 2013 at 8:22 PM, Tejun Heo t...@kernel.org wrote: On Fri, Apr 26, 2013 at 07:40:20PM +0200, Sedat Dilek wrote: Oops, NULL-pointer-deref [ __queue_work() ] [ 25.974932] BUG: unable to handle kernel NULL pointer dereference at 0100 [ 25.974944] IP:

Re: linux-next: Tree for Apr 26

2013-04-26 Thread Yann E. MORIN
Michal, Sedat, All, On Fri, Apr 26, 2013 at 01:13:33PM +0200, Michal Marek wrote: On 26.4.2013 13:08, Michal Marek wrote: On 26.4.2013 12:49, Sedat Dilek wrote: With reverting all kbuild-next commits I was able to build again. Revert kconfig: implement KCONFIG_PROBABILITY for

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-04-26 Thread Tejun Heo
On Fri, Apr 26, 2013 at 11:07:44PM +0200, Sedat Dilek wrote: The second argument %rsi is zero, which got transferred to %r13 and then offset deref on it trapped. The second argument is @wq and the oopsing code is the wq-flags deref in the following if condition. /* if dying,

Re: linux-next: Tree for Apr 26 [ bluetooth on suspend/resume ]

2013-04-26 Thread Sedat Dilek
On Sat, Apr 27, 2013 at 12:04 AM, Tejun Heo t...@kernel.org wrote: On Fri, Apr 26, 2013 at 11:07:44PM +0200, Sedat Dilek wrote: The second argument %rsi is zero, which got transferred to %r13 and then offset deref on it trapped. The second argument is @wq and the oopsing code is the