Re: linux-next: Tree for Dec 21 (objtool warning)

On 12/22/20 9:09 PM, Josh Poimboeuf wrote: > On Mon, Dec 21, 2020 at 08:03:17AM -0800, Randy Dunlap wrote: >> On 12/20/20 7:18 PM, Stephen Rothwell wrote: >>> Hi all, >>> >>> News: there will be no linux-next releases between Dec 24 and Jan >>> 3 inclusive. >>> >>> Please do not add any v5.12

Re: linux-next: Tree for Dec 21 (objtool warning)

On Mon, Dec 21, 2020 at 08:03:17AM -0800, Randy Dunlap wrote: > On 12/20/20 7:18 PM, Stephen Rothwell wrote: > > Hi all, > > > > News: there will be no linux-next releases between Dec 24 and Jan > > 3 inclusive. > > > > Please do not add any v5.12 destined code to your linux-next included > >

Re: linux-next: Tree for Dec 21 (objtool warning)

On 12/20/20 7:18 PM, Stephen Rothwell wrote: > Hi all, > > News: there will be no linux-next releases between Dec 24 and Jan > 3 inclusive. > > Please do not add any v5.12 destined code to your linux-next included > branches until after v5.11-rc1 has been released. > > Changes since 20201218: >

linux-next: Tree for Dec 21

Hi all, News: there will be no linux-next releases between Dec 24 and Jan 3 inclusive. Please do not add any v5.12 destined code to your linux-next included branches until after v5.11-rc1 has been released. Changes since 20201218: New trees: clk-renesas and pinctrl-renesas The notifications

Re: linux-next: Tree for Dec 21

On 21-12-18, 08:21, Guenter Roeck wrote: > On Fri, Dec 21, 2018 at 07:32:44PM +1100, Stephen Rothwell wrote: > [6]: > > Build failure. > > # bad: [340ae71f9dd421227a58c14a909b63033745dca4] Add linux-next specific > files for 20181221 > # good: [7566ec393f4161572ba6f11ad5171fd5d59b0fbd] Linux

Re: linux-next: Tree for Dec 21

On Fri, Dec 21, 2018 at 08:21:49AM -0800, Guenter Roeck wrote: > --- > [5]: > > The bisect is old, but still applies. Revering the offending patch fixes the > problem. > > # bad: [8c9733fd9806c71e7f2313a280f98cb3051f93df] Add linux-next specific > files for 20181123 > # good:

Re: linux-next: Tree for Dec 21

On Friday, December 21, 2018 9:51:49 PM IST Guenter Roeck wrote: > On Fri, Dec 21, 2018 at 07:32:44PM +1100, Stephen Rothwell wrote: > > Hi all, > > > > News: there will be no linux-next release until Jan 2. Have a good break. > > > > Changes since 20181220: > > > > New tree: gpio-brgl > > >

Re: linux-next: Tree for Dec 21 (acpi without CONFIG_PCI)

On 12/21/2018 6:43 PM, Randy Dunlap wrote: Any other issues? There are a few Kconfig dependency issues. Here are 2 of them: WARNING: unmet direct dependencies detected for VGA_ARB Depends on [n]: HAS_IOMEM [=y] && PCI [=n] && !S390 Selected by [y]: - VGA_SWITCHEROO [=y] && HAS_IOMEM

Re: linux-next: Tree for Dec 21 (acpi without CONFIG_PCI)

On 12/21/2018 7:28 PM, Randy Dunlap wrote: Any other issues? and on i386, there is this additional kconfig warning: WARNING: unmet direct dependencies detected for INTEL_SOC_DTS_IOSF_CORE Depends on [n]: THERMAL [=y] && (X86 [=y] || X86_INTEL_QUARK [=n] || COMPILE_TEST [=n]) && X86 [=y]

Re: linux-next: Tree for Dec 21 (nvdimm/security.o)

On Fri, Dec 21, 2018 at 10:51 AM Dan Williams wrote: > > On Fri, Dec 21, 2018 at 10:44 AM Randy Dunlap wrote: > > > > On 12/21/18 12:32 AM, Stephen Rothwell wrote: > > > Hi all, > > > > > > News: there will be no linux-next release until Jan 2. Have a good break. > > > > > > Changes since

Re: linux-next: Tree for Dec 21

Guenter Roeck wrote: > mips:cavium_octeon_defconfig [4] > git bisect bad 4165079ba328dd47262a2183049d3591f0a750b1 > # first bad commit: [4165079ba328dd47262a2183049d3591f0a750b1] net: switch > secpath to use skb extension infrastructure Indeed, sorry. staging/octeon needs a small fix.

Re: [alsa-devel] linux-next: Tree for Dec 21 (SND_HDA_INTEL_DSP_DETECTION)

On 12/21/18 12:02 PM, Randy Dunlap wrote: On 12/21/18 12:32 AM, Stephen Rothwell wrote: Hi all, News: there will be no linux-next release until Jan 2. Have a good break. Changes since 20181220: on x86_64: A new group of Kconfig "select"s is causing kconfig warnings: WARNING: unmet

Re: linux-next: Tree for Dec 21 (nvdimm/security.o)

On Fri, Dec 21, 2018 at 10:44 AM Randy Dunlap wrote: > > On 12/21/18 12:32 AM, Stephen Rothwell wrote: > > Hi all, > > > > News: there will be no linux-next release until Jan 2. Have a good break. > > > > Changes since 20181220: > > > > on x86_64: > > ld: drivers/nvdimm/security.o: in function

Re: linux-next: Tree for Dec 21 (FB_BACKLIGHT)

On 12/21/18 12:32 AM, Stephen Rothwell wrote: > Hi all, > > News: there will be no linux-next release until Jan 2. Have a good break. > > Changes since 20181220: > on x86_64: WARNING: unmet direct dependencies detected for FB_BACKLIGHT Depends on [m]: HAS_IOMEM [=y] && FB [=m] Selected

Re: linux-next: Tree for Dec 21 (acpi without CONFIG_PCI)

On 12/21/18 9:23 AM, Sinan Kaya wrote: > > > On Friday, December 21, 2018, Randy Dunlap > wrote: > > On 12/21/18 12:32 AM, Stephen Rothwell wrote: > > Hi all, > > > > News: there will be no linux-next release until Jan 2.  Have a good > break. >

Re: linux-next: Tree for Dec 21 (SND_HDA_INTEL_DSP_DETECTION)

On 12/21/18 12:32 AM, Stephen Rothwell wrote: > Hi all, > > News: there will be no linux-next release until Jan 2. Have a good break. > > Changes since 20181220: > on x86_64: A new group of Kconfig "select"s is causing kconfig warnings: WARNING: unmet direct dependencies detected for

Re: linux-next: Tree for Dec 21 (acpi without CONFIG_PCI)

On 12/21/18 9:23 AM, Sinan Kaya wrote: > > > On Friday, December 21, 2018, Randy Dunlap > wrote: > > On 12/21/18 12:32 AM, Stephen Rothwell wrote: > > Hi all, > > > > News: there will be no linux-next release until Jan 2.  Have a good > break. >

Re: linux-next: Tree for Dec 21 (mmc/host/sdhci-omap.c)

On 12/21/18 12:32 AM, Stephen Rothwell wrote: > Hi all, > > News: there will be no linux-next release until Jan 2. Have a good break. > > Changes since 20181220: > on x86_64: This change to drivers/mmc/host/Kconfig: config MMC_SDHCI_OMAP tristate "TI SDHCI Controller Support"

Re: linux-next: Tree for Dec 21 (acpi without CONFIG_PCI)

On 12/21/18 9:23 AM, Sinan Kaya wrote: > > > On Friday, December 21, 2018, Randy Dunlap > wrote: > > On 12/21/18 12:32 AM, Stephen Rothwell wrote: > > Hi all, > > > > News: there will be no linux-next release until Jan 2.  Have a good > break. >

Re: linux-next: Tree for Dec 21 (nvdimm/security.o)

On 12/21/18 12:32 AM, Stephen Rothwell wrote: > Hi all, > > News: there will be no linux-next release until Jan 2. Have a good break. > > Changes since 20181220: > on x86_64: ld: drivers/nvdimm/security.o: in function `nvdimm_request_key': security.c:(.text+0xbe): undefined reference to

Re: linux-next: Tree for Dec 21 (acpi without CONFIG_PCI)

On 12/21/18 12:32 AM, Stephen Rothwell wrote: > Hi all, > > News: there will be no linux-next release until Jan 2. Have a good break. > > Changes since 20181220: > on i386 or x86_64: ../drivers/acpi/acpi_lpss.c: In function 'acpi_lpss_find_device': ../drivers/acpi/acpi_lpss.c:538:26: error:

Re: linux-next: Tree for Dec 21

On Fri, 21 Dec 2018 at 17:21, Guenter Roeck wrote: > ... > --- > [8]: > > This problem results in a stall on reboot. Reverting the offending patch > fixes the problem. > > # bad: [340ae71f9dd421227a58c14a909b63033745dca4] Add linux-next specific > files for 20181221 > # good:

Re: linux-next: Tree for Dec 21

On Fri, Dec 21, 2018 at 07:32:44PM +1100, Stephen Rothwell wrote: > Hi all, > > News: there will be no linux-next release until Jan 2. Have a good break. > > Changes since 20181220: > > New tree: gpio-brgl > > The pm tree gained a conflict against the kbuild tree. > > The bpf-next tree

linux-next: Tree for Dec 21

Hi all, News: there will be no linux-next release until Jan 2. Have a good break. Changes since 20181220: New tree: gpio-brgl The pm tree gained a conflict against the kbuild tree. The bpf-next tree gained a conflict against Linus' tree. The kvm tree gained a conflict against the powerpc

linux-next: Tree for Dec 21

Hi all, News: tomorrow will be the last linux-next for 2017. The next release (after tomorrow) will be on January 2nd. Changes since 20171220: The net-next tree gained a conflict against the net tree. It also gained a build failure due to an interaction with the net tree for which I applied a

linux-next: Tree for Dec 21

Hi all, News: tomorrow will be the last linux-next for 2017. The next release (after tomorrow) will be on January 2nd. Changes since 20171220: The net-next tree gained a conflict against the net tree. It also gained a build failure due to an interaction with the net tree for which I applied a

linux-next: Tree for Dec 21

Hi all, Please do not add any material for v4.11 to your linux-next included branches until after v4.10-rc1 has been released. There will be no linux-next releases from me between Dec 24 and Jan 2 inclusive (unless I get really bored with my new toys :-)). Changes since 20161220: Non-merge

linux-next: Tree for Dec 21

Hi all, Please do not add any material for v4.11 to your linux-next included branches until after v4.10-rc1 has been released. There will be no linux-next releases from me between Dec 24 and Jan 2 inclusive (unless I get really bored with my new toys :-)). Changes since 20161220: Non-merge

Re: linux-next: Tree for Dec 21 (logfs)

On 12/21/15 00:05, Stephen Rothwell wrote: > Hi all, > > Changes since 20151218: > on i386 or x86_64: when CONFIG_MTD=m and CONFIG_LOGFS=y: fs/built-in.o: In function `logfs_mount': super.c:(.text+0xb695e): undefined reference to `logfs_get_sb_mtd' fs/built-in.o: In function

linux-next: Tree for Dec 21

Hi all, Changes since 20151218: The orangefs tree gained a conflict against Linus' tree. The i2c tree still had its build failure for which I applied a patch. The clockevents tree lost its build failure but gained a conflict against the tip tree. The cgroup tree gained conflict against the

linux-next: Tree for Dec 21

Hi all, Changes since 20151218: The orangefs tree gained a conflict against Linus' tree. The i2c tree still had its build failure for which I applied a patch. The clockevents tree lost its build failure but gained a conflict against the tip tree. The cgroup tree gained conflict against the

Re: linux-next: Tree for Dec 21 (logfs)

On 12/21/15 00:05, Stephen Rothwell wrote: > Hi all, > > Changes since 20151218: > on i386 or x86_64: when CONFIG_MTD=m and CONFIG_LOGFS=y: fs/built-in.o: In function `logfs_mount': super.c:(.text+0xb695e): undefined reference to `logfs_get_sb_mtd' fs/built-in.o: In function

linux-next: Tree for Dec 21

Hi all, There will only be intermittent releases of linux-next between now and Jan 5. Changes since 20141219: The idle tree gained a conflict against Linus' tree. The akpm tree lost a patch that turned up elsewhere. Non-merge commits (relative to Linus' tree): 375 445 files changed, 10391

linux-next: Tree for Dec 21

Hi all, There will only be intermittent releases of linux-next between now and Jan 5. Changes since 20141219: The idle tree gained a conflict against Linus' tree. The akpm tree lost a patch that turned up elsewhere. Non-merge commits (relative to Linus' tree): 375 445 files changed, 10391

linux-next: Tree for Dec 21

Hi all, Changes since 20121220: Lots of conflicts are migrating between trees. The infiniband tree lost its build failure. The arm-soc tree gained a conflict against the pinctrl tree. The signal tree gained conflicts against Linus' tree.

linux-next: Tree for Dec 21

Hi all, Changes since 20121220: Lots of conflicts are migrating between trees. The infiniband tree lost its build failure. The arm-soc tree gained a conflict against the pinctrl tree. The signal tree gained conflicts against Linus' tree.