Re: linux-next: Tree for Oct 29 [drivers/nvdimm/nd_e820.ko]

2020-10-29 Thread Randy Dunlap
On 10/28/20 9:55 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20201028: > on x86_64: ERROR: modpost: "phys_to_target_node" [drivers/nvdimm/nd_e820.ko] undefined! Full randconfig file is attached. -- ~Randy Reported-by: Randy Dunlap # # Automatically generated file; DO NOT EDIT.

linux-next: Tree for Oct 29

2020-10-29 Thread Stephen Rothwell
Hi all, Changes since 20201028: The samsung-krzk-fixes tree gained a conflict against the arm-soc-fixes tree. The drm-misc tree gained a conflict against the drm-misc-fixes tree. The phy-next tree gained a conflict against the regulator-fixes tree. The staging tree gained a conflict against th

Re: [sysadmin] Re: linux-next: Tree for Oct 29

2018-10-29 Thread Konstantin Ryabitsev
On Mon, Oct 29, 2018 at 01:16:59PM +0100, Geert Uytterhoeven wrote: > I can confirm syd.git.kernel.org and ord.git.kernel.org have it, but > fra.git.kernel.org (my default) hasn't. The Frankfurt frontend lost the VPN connection to our main infra. I'm checking why the alerts for that didn't fire pr

Re: linux-next: Tree for Oct 29

2018-10-29 Thread damian
On Mon, 29. Oct 20:41, Stephen Rothwell wrote: > Hi Damian, > > On Mon, 29 Oct 2018 07:33:19 +0100 Damian Tometzki > wrote: > > > > on the site isnt available the new linux-next ? > > Only the old one. > > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > > It seems to

Re: linux-next: Tree for Oct 29

2018-10-29 Thread Geert Uytterhoeven
On Mon, Oct 29, 2018 at 1:09 PM Stephen Rothwell wrote: > On Mon, 29 Oct 2018 12:42:26 +0100 damian wrote: > > On Mon, 29. Oct 20:41, Stephen Rothwell wrote: > > > On Mon, 29 Oct 2018 07:33:19 +0100 Damian Tometzki > > > wrote: > > > > > > > > on the site isnt available the new linux-next ? > >

Re: linux-next: Tree for Oct 29

2018-10-29 Thread Stephen Rothwell
Hi Damian, On Mon, 29 Oct 2018 12:42:26 +0100 damian wrote: > > On Mon, 29. Oct 20:41, Stephen Rothwell wrote: > > > > On Mon, 29 Oct 2018 07:33:19 +0100 Damian Tometzki > > wrote: > > > > > > on the site isnt available the new linux-next ? > > > Only the old one. > > > > > > https://git.k

Re: linux-next: Tree for Oct 29

2018-10-29 Thread Stephen Rothwell
Hi Damian, On Mon, 29 Oct 2018 07:33:19 +0100 Damian Tometzki wrote: > > on the site isnt available the new linux-next ? > Only the old one. > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git It seems to be there now (at least for me). Maybe just mirroring delays? -- Ch

Re: linux-next: Tree for Oct 29

2018-10-28 Thread Damian Tometzki
On Mo, 29. Okt 17:02, Stephen Rothwell wrote: > Hi all, > Hello Stephen, on the site isnt available the new linux-next ? Only the old one. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > Changes since 20181019: > > Linus' tree gained 2 build failures for which I reverted

linux-next: Tree for Oct 29

2018-10-28 Thread Stephen Rothwell
Hi all, Changes since 20181019: Linus' tree gained 2 build failures for which I reverted a commit and added a fix patch. The arm-soc tree gained conflicts against Linus' tree. The vfs tree gained conflicts against the ceph and nfsd trees. The pm tree gained conflicts against Linus' and the i2c

linux-next: Tree for Oct 29

2014-10-28 Thread Stephen Rothwell
Hi all, Changes since 20141028: The usb-gadget-fixes tree gained a build failure so I used the version from next-20141028. The net-next tree gained a conflict against the net tree. The bluetooth tree lost its build failure. The pinctrl tree lost its build failure. Non-merge commits (relative

linux-next: Tree for Oct 29

2013-10-29 Thread Stephen Rothwell
Hi all, A big thank you to Thierry Reding and Mark Brown for jumping in and keeping things ticking over while I was away. Changes since 20130927: Removed tree: scsi-post-merge (not being used - will be replaced if needed) Lots of new conflicts and build failures (some of which have been fixed s

Re: linux-next: Tree for Oct 29 (tty->raw)

2012-10-29 Thread Greg Kroah-Hartman
On Sun, Oct 28, 2012 at 09:17:09PM -0700, Randy Dunlap wrote: > On 10/28/2012 08:46 PM, Stephen Rothwell wrote: > > > Hi all, > > > > Changes since 20121026: > > > > > Who made some changes that remove tty->raw ? Jiri did. > There is still one occurrence in arch/um that is causing > a build

Re: linux-next: Tree for Oct 29 (tty->raw)

2012-10-28 Thread Randy Dunlap
On 10/28/2012 08:46 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20121026: > Who made some changes that remove tty->raw ? There is still one occurrence in arch/um that is causing a build error (on x86_64 defconfig): arch/um/drivers/chan_kern.c: In function 'tty_receive_char': arch

linux-next: Tree for Oct 29

2012-10-28 Thread Stephen Rothwell
Hi all, Changes since 20121026: New tree: bcm2835 The v4l-dvb tree gained a build failure so I used the version from next-20121026. The sound-asoc tree gained a build failure so I used the version from next-20121026. The signal tree gained a conflict against the sparc tree. The akpm tree gain