linux-next: Tree for Feb 12

2021-02-12 Thread Stephen Rothwell
Hi all,

Changes since 20210211:

The powerpc tree lost its build failure.

The btrfs tree gained a conflict against the fscache tree.

The net-next tree gained a conflict against the net tree.

The device-mapper tree lost its build failure.

The spi tree gained a conflict against the powerpc tree.

The akpm-current tree gained a conflict against the fscache tree.

Non-merge commits (relative to Linus' tree): 10010
 10213 files changed, 409821 insertions(+), 275217 deletions(-)



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log
files in the Next directory.  Between each merge, the tree was built
with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
multi_v7_defconfig for arm and a native build of tools/perf. After
the final fixups (if any), I do an x86_64 modules_install followed by
builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
and sparc64 defconfig and htmldocs. And finally, a simple boot test
of the powerpc pseries_le_defconfig kernel in qemu (with and without
kvm enabled).

Below is a summary of the state of the merge.

I am currently merging 333 trees (counting Linus' and 87 trees of bug
fix patches pending for the current merge release).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

-- 
Cheers,
Stephen Rothwell

$ git checkout master
$ git reset --hard stable
Merging origin/master (c05263df6c1a Merge tag 'gpio-fixes-for-v5.11' of 
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux)
Merging fixes/fixes (e71ba9452f0b Linux 5.11-rc2)
Merging kbuild-current/fixes (29500f15b54b kbuild: fix CONFIG_TRIM_UNUSED_KSYMS 
build for ppc64)
Merging arc-current/for-curr (7c53f6b671f4 Linux 5.11-rc3)
Merging arm-current/fixes (4d62e81b60d4 ARM: kexec: fix oops after TLB are 
invalidated)
Merging arm64-fixes/for-next/fixes (22cd5edb2d9c arm64: Use simpler arithmetics 
for the linear map macros)
Merging arm-soc-fixes/arm/fixes (090e502e4e63 Merge tag 
'socfpga_dts_fix_for_v5.12' of 
git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux into arm/fixes)
Merging drivers-memory-fixes/fixes (5c8fe583cce5 Linux 5.11-rc1)
Merging m68k-current/for-linus (2ae92e8b9b7e MAINTAINERS: Update m68k Mac entry)
Merging powerpc-fixes/fixes (8c511eff1827 powerpc/kuap: Allow kernel thread to 
access userspace after kthread_use_mm)
Merging s390-fixes/fixes (92bf22614b21 Linux 5.11-rc7)
Merging sparc/master (0a95a6d1a4cd sparc: use for_each_child_of_node() macro)
Merging fscrypt-current/for-stable (d19d8d345eec fscrypt: fix inline encryption 
not used on new files)
Merging net/master (f1d77b2efbe6 netdev-FAQ: answer some questions about the 
patchwork checks)
Merging bpf/master (732fa3233066 selftests/bpf: Convert test_xdp_redirect.sh to 
bash)
Merging ipsec/master (da64ae2d35d3 xfrm: Fix wraparound in 
xfrm_policy_addr_delta())
Merging netfilter/master (450bbc339518 Merge 
git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf)
Merging ipvs/master (44a674d6f798 Merge tag 'mlx5-fixes-2021-01-26' of 
git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux)
Merging wireless-drivers/master (93a1d4791c10 mt76: dma: fix a possible memory 
leak in mt76_add_fragment())
Merging mac80211/master (b3d2c7b876d4 Merge 
git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf)
Merging rdma-fixes/for-rc (1048ba83fb1c Linux 5.11-rc6)
Merging sound-current/for-linus (056a3da5d07f ALSA: hda/hdmi: Drop bogus check 
at closing a stream)
Merging sound-asoc-fixes/for-linus (c8bca765c4ab Merge remote-tracking branch 
'asoc/for-5.11' into asoc-linus)
Merging regmap-fixes/for-linus (19c329f68089 Linux 5.11-rc4)
Merging regulator-fixes/for-linus (95a5122b3139 Merge remote-tracking branch 
'regulator/for-5.11' into regulator-linus)
Merging spi-fixes/for-linus (eddaece2173b Merge remote-tracking branch 
'spi/for-5.11' into spi-linus)
Merging pci-current/for-linus (7e69d07d7c3c Revert "PCI/ASPM: Save/restore L1SS 
Capability for suspend/resume")
Merging driver-core.current/driver-core-linus (6ee1d745b7c9 Linux 5.11-rc5)
Merging 

Re: linux-next: Tree for Feb 12 (chrome/wilco_ec/)

2019-02-13 Thread Randy Dunlap
On 2/13/19 9:26 AM, Nick Crews wrote:
> Randy,
> 
> No, I didn't test it, I'm sorry, of course I should done that.
> Sorry for the formatting too, I'm new to this and wasn't sure what
> tool to use. The following version of the patch was made with
> "git format-patch" and now I'm replying in plaintext, it hopefully is better.
> 

Hi Nick,

A few small comments:

> From 0cfb3db970636983c1570827b7793e31e352716e Mon Sep 17 00:00:00 2001
> From: Nick Crews 
> Date: Tue, 12 Feb 2019 16:46:15 -0700
> Subject: [PATCH] FROMLIST: wilco_ec: Fix Kconfig dependencies

delete FROMLIST:

The Subject should include a subsystem reference, e.g.:

[PATCH] chrome: fix wilco_ex Kconfig dependencies


> 
> In the initial version of the Wilco EC Driver, the
> dependency order was wrong. It before was possible to
> select CONFIG_WILCO_EC and CONFIG_CROS_EC_LPC without
> having CONFIG_CROS_EC_LPC_MEC. This was wrong, since
> WILCO_EC depends upon CONFIG CROS_EC_LPC_MEC, not the
> other way around.
> 

More importantly, the patch is still whitespace-damaged.
The Kconfig file lines that begin with "bool", "depends", "help", etc.
should contain a tab.  Maybe your email client mangled the whitespace.

You might need to take a look at Documentation/process/email-clients.rst
for some hints.

Or if you email the patch with "git send-email", it might be fine.

Aside from that, after I fixed the whitespace, the kernel build does work
without errors.

Thanks.

> ---
>  drivers/platform/chrome/Kconfig  | 2 +-
>  drivers/platform/chrome/wilco_ec/Kconfig | 3 +--
>  2 files changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/platform/chrome/Kconfig b/drivers/platform/chrome/Kconfig
> index 462eb9dfa4f2..b69561050868 100644
> --- a/drivers/platform/chrome/Kconfig
> +++ b/drivers/platform/chrome/Kconfig
> @@ -95,7 +95,7 @@ config CROS_EC_LPC
> 
>  config CROS_EC_LPC_MEC
>   bool "ChromeOS Embedded Controller LPC Microchip EC (MEC) variant"
> - depends on CROS_EC_LPC || WILCO_EC
> + depends on CROS_EC_LPC
>   default n
>   help
> If you say Y here, a variant LPC protocol for the Microchip EC
> diff --git a/drivers/platform/chrome/wilco_ec/Kconfig
> b/drivers/platform/chrome/wilco_ec/Kconfig
> index d8e2cddb4712..de097690fce3 100644
> --- a/drivers/platform/chrome/wilco_ec/Kconfig
> +++ b/drivers/platform/chrome/wilco_ec/Kconfig
> @@ -1,7 +1,6 @@
>  config WILCO_EC
>   tristate "ChromeOS Wilco Embedded Controller"
> - depends on ACPI && X86
> - select CROS_EC_LPC_MEC
> + depends on ACPI && X86 && CROS_EC_LPC_MEC
>   help
> If you say Y here, you get support for talking to the ChromeOS
> Wilco EC over an eSPI bus. This uses a simple byte-level protocol
> --
> 2.20.1
> 
> 
> On Tue, Feb 12, 2019 at 5:13 PM Randy Dunlap  wrote:
>>
>> On 2/12/19 3:49 PM, Nick Crews wrote:
>>> OK, here is the patch to fix this problem. We had the dependency backwards.
>>>
>>> Should I re-send out the entire patch series to the LKML with this fix in 
>>> it?
>>>
>>>
>>> diff --git a/drivers/platform/chrome/Kconfig 
>>> b/drivers/platform/chrome/Kconfig
>>> index 462eb9dfa4f2..b69561050868 100644
>>> --- a/drivers/platform/chrome/Kconfig
>>> +++ b/drivers/platform/chrome/Kconfig
>>> @@ -95,7 +95,7 @@ config CROS_EC_LPC
>>>
>>>  config CROS_EC_LPC_MEC
>>> bool "ChromeOS Embedded Controller LPC Microchip EC (MEC) variant"
>>> -   depends on CROS_EC_LPC || WILCO_EC
>>> +   depends on CROS_EC_LPC
>>> default n
>>> help
>>>   If you say Y here, a variant LPC protocol for the Microchip EC
>>> diff --git a/drivers/platform/chrome/wilco_ec/Kconfig 
>>> b/drivers/platform/chrome/wilco_ec/Kconfig
>>> index d8e2cddb4712..6ea2d3f64ce5 100644
>>> --- a/drivers/platform/chrome/wilco_ec/Kconfig
>>> +++ b/drivers/platform/chrome/wilco_ec/Kconfig
>>> @@ -1,6 +1,6 @@
>>>  config WILCO_EC
>>> tristate "ChromeOS Wilco Embedded Controller"
>>> -   depends on ACPI && X86
>>> +   depends on ACPI && X86 && CROS_EC_LPC_MEC
>>> select CROS_EC_LPC_MEC
>>> help
>>>   If you say Y here, you get support for talking to the ChromeOS
>>>
>>>
>>
>> Nick,
>>
>> Did you test this?
>>
>> When I apply the patch (by hand, since it was whitespace-mangled/damaged),
>> I get this:
>>
>> rdunlap@midway:linux-next-20190212> make ARCH=x86_64 O=X64 oldconfig
>> make[1]: Entering directory '/home/rdunlap/lnx/next/linux-next-20190212/X64'
>>   GEN Makefile
>> scripts/kconfig/conf  --oldconfig Kconfig
>> drivers/platform/chrome/Kconfig:84:error: recursive dependency detected!
>> drivers/platform/chrome/Kconfig:84: symbol CROS_EC_LPC_MEC is selected 
>> by WILCO_EC
>> drivers/platform/chrome/wilco_ec/Kconfig:1: symbol WILCO_EC depends on 
>> CROS_EC_LPC_MEC
>> For a resolution refer to Documentation/kbuild/kconfig-language.txt
>> subsection "Kconfig recursive dependency limitations"
>>
>>
>>
>>
>> --
>> ~Randy


-- 
~Randy


Re: linux-next: Tree for Feb 12 (chrome/wilco_ec/)

2019-02-13 Thread Nick Crews
Randy,

No, I didn't test it, I'm sorry, of course I should done that.
Sorry for the formatting too, I'm new to this and wasn't sure what
tool to use. The following version of the patch was made with
"git format-patch" and now I'm replying in plaintext, it hopefully is better.

>From 0cfb3db970636983c1570827b7793e31e352716e Mon Sep 17 00:00:00 2001
From: Nick Crews 
Date: Tue, 12 Feb 2019 16:46:15 -0700
Subject: [PATCH] FROMLIST: wilco_ec: Fix Kconfig dependencies

In the initial version of the Wilco EC Driver, the
dependency order was wrong. It before was possible to
select CONFIG_WILCO_EC and CONFIG_CROS_EC_LPC without
having CONFIG_CROS_EC_LPC_MEC. This was wrong, since
WILCO_EC depends upon CONFIG CROS_EC_LPC_MEC, not the
other way around.

---
 drivers/platform/chrome/Kconfig  | 2 +-
 drivers/platform/chrome/wilco_ec/Kconfig | 3 +--
 2 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/drivers/platform/chrome/Kconfig b/drivers/platform/chrome/Kconfig
index 462eb9dfa4f2..b69561050868 100644
--- a/drivers/platform/chrome/Kconfig
+++ b/drivers/platform/chrome/Kconfig
@@ -95,7 +95,7 @@ config CROS_EC_LPC

 config CROS_EC_LPC_MEC
  bool "ChromeOS Embedded Controller LPC Microchip EC (MEC) variant"
- depends on CROS_EC_LPC || WILCO_EC
+ depends on CROS_EC_LPC
  default n
  help
If you say Y here, a variant LPC protocol for the Microchip EC
diff --git a/drivers/platform/chrome/wilco_ec/Kconfig
b/drivers/platform/chrome/wilco_ec/Kconfig
index d8e2cddb4712..de097690fce3 100644
--- a/drivers/platform/chrome/wilco_ec/Kconfig
+++ b/drivers/platform/chrome/wilco_ec/Kconfig
@@ -1,7 +1,6 @@
 config WILCO_EC
  tristate "ChromeOS Wilco Embedded Controller"
- depends on ACPI && X86
- select CROS_EC_LPC_MEC
+ depends on ACPI && X86 && CROS_EC_LPC_MEC
  help
If you say Y here, you get support for talking to the ChromeOS
Wilco EC over an eSPI bus. This uses a simple byte-level protocol
--
2.20.1


On Tue, Feb 12, 2019 at 5:13 PM Randy Dunlap  wrote:
>
> On 2/12/19 3:49 PM, Nick Crews wrote:
> > OK, here is the patch to fix this problem. We had the dependency backwards.
> >
> > Should I re-send out the entire patch series to the LKML with this fix in 
> > it?
> >
> >
> > diff --git a/drivers/platform/chrome/Kconfig 
> > b/drivers/platform/chrome/Kconfig
> > index 462eb9dfa4f2..b69561050868 100644
> > --- a/drivers/platform/chrome/Kconfig
> > +++ b/drivers/platform/chrome/Kconfig
> > @@ -95,7 +95,7 @@ config CROS_EC_LPC
> >
> >  config CROS_EC_LPC_MEC
> > bool "ChromeOS Embedded Controller LPC Microchip EC (MEC) variant"
> > -   depends on CROS_EC_LPC || WILCO_EC
> > +   depends on CROS_EC_LPC
> > default n
> > help
> >   If you say Y here, a variant LPC protocol for the Microchip EC
> > diff --git a/drivers/platform/chrome/wilco_ec/Kconfig 
> > b/drivers/platform/chrome/wilco_ec/Kconfig
> > index d8e2cddb4712..6ea2d3f64ce5 100644
> > --- a/drivers/platform/chrome/wilco_ec/Kconfig
> > +++ b/drivers/platform/chrome/wilco_ec/Kconfig
> > @@ -1,6 +1,6 @@
> >  config WILCO_EC
> > tristate "ChromeOS Wilco Embedded Controller"
> > -   depends on ACPI && X86
> > +   depends on ACPI && X86 && CROS_EC_LPC_MEC
> > select CROS_EC_LPC_MEC
> > help
> >   If you say Y here, you get support for talking to the ChromeOS
> >
> >
>
> Nick,
>
> Did you test this?
>
> When I apply the patch (by hand, since it was whitespace-mangled/damaged),
> I get this:
>
> rdunlap@midway:linux-next-20190212> make ARCH=x86_64 O=X64 oldconfig
> make[1]: Entering directory '/home/rdunlap/lnx/next/linux-next-20190212/X64'
>   GEN Makefile
> scripts/kconfig/conf  --oldconfig Kconfig
> drivers/platform/chrome/Kconfig:84:error: recursive dependency detected!
> drivers/platform/chrome/Kconfig:84: symbol CROS_EC_LPC_MEC is selected by 
> WILCO_EC
> drivers/platform/chrome/wilco_ec/Kconfig:1: symbol WILCO_EC depends on 
> CROS_EC_LPC_MEC
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
>
>
>
>
> --
> ~Randy


Re: linux-next: Tree for Feb 12 (chrome/wilco_ec/)

2019-02-12 Thread Randy Dunlap
On 2/12/19 3:49 PM, Nick Crews wrote:
> OK, here is the patch to fix this problem. We had the dependency backwards.
> 
> Should I re-send out the entire patch series to the LKML with this fix in it?
> 
> 
> diff --git a/drivers/platform/chrome/Kconfig b/drivers/platform/chrome/Kconfig
> index 462eb9dfa4f2..b69561050868 100644
> --- a/drivers/platform/chrome/Kconfig
> +++ b/drivers/platform/chrome/Kconfig
> @@ -95,7 +95,7 @@ config CROS_EC_LPC
>  
>  config CROS_EC_LPC_MEC
>         bool "ChromeOS Embedded Controller LPC Microchip EC (MEC) variant"
> -       depends on CROS_EC_LPC || WILCO_EC
> +       depends on CROS_EC_LPC
>         default n
>         help
>           If you say Y here, a variant LPC protocol for the Microchip EC
> diff --git a/drivers/platform/chrome/wilco_ec/Kconfig 
> b/drivers/platform/chrome/wilco_ec/Kconfig
> index d8e2cddb4712..6ea2d3f64ce5 100644
> --- a/drivers/platform/chrome/wilco_ec/Kconfig
> +++ b/drivers/platform/chrome/wilco_ec/Kconfig
> @@ -1,6 +1,6 @@
>  config WILCO_EC
>         tristate "ChromeOS Wilco Embedded Controller"
> -       depends on ACPI && X86
> +       depends on ACPI && X86 && CROS_EC_LPC_MEC
>         select CROS_EC_LPC_MEC
>         help
>           If you say Y here, you get support for talking to the ChromeOS
> 
> 

Nick,

Did you test this?

When I apply the patch (by hand, since it was whitespace-mangled/damaged),
I get this:

rdunlap@midway:linux-next-20190212> make ARCH=x86_64 O=X64 oldconfig
make[1]: Entering directory '/home/rdunlap/lnx/next/linux-next-20190212/X64'
  GEN Makefile
scripts/kconfig/conf  --oldconfig Kconfig
drivers/platform/chrome/Kconfig:84:error: recursive dependency detected!
drivers/platform/chrome/Kconfig:84: symbol CROS_EC_LPC_MEC is selected by 
WILCO_EC
drivers/platform/chrome/wilco_ec/Kconfig:1: symbol WILCO_EC depends on 
CROS_EC_LPC_MEC
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"




-- 
~Randy


Re: linux-next: Tree for Feb 12 (chrome/wilco_ec/)

2019-02-12 Thread Randy Dunlap
On 2/12/19 3:49 PM, Nick Crews wrote:
> OK, here is the patch to fix this problem. We had the dependency backwards.
> 
> Should I re-send out the entire patch series to the LKML with this fix in it?
> 
> 
> diff --git a/drivers/platform/chrome/Kconfig b/drivers/platform/chrome/Kconfig
> index 462eb9dfa4f2..b69561050868 100644
> --- a/drivers/platform/chrome/Kconfig
> +++ b/drivers/platform/chrome/Kconfig
> @@ -95,7 +95,7 @@ config CROS_EC_LPC
>  
>  config CROS_EC_LPC_MEC
>         bool "ChromeOS Embedded Controller LPC Microchip EC (MEC) variant"
> -       depends on CROS_EC_LPC || WILCO_EC
> +       depends on CROS_EC_LPC
>         default n
>         help
>           If you say Y here, a variant LPC protocol for the Microchip EC
> diff --git a/drivers/platform/chrome/wilco_ec/Kconfig 
> b/drivers/platform/chrome/wilco_ec/Kconfig
> index d8e2cddb4712..6ea2d3f64ce5 100644
> --- a/drivers/platform/chrome/wilco_ec/Kconfig
> +++ b/drivers/platform/chrome/wilco_ec/Kconfig
> @@ -1,6 +1,6 @@
>  config WILCO_EC
>         tristate "ChromeOS Wilco Embedded Controller"
> -       depends on ACPI && X86
> +       depends on ACPI && X86 && CROS_EC_LPC_MEC
>         select CROS_EC_LPC_MEC
>         help
>           If you say Y here, you get support for talking to the ChromeOS
> 
> 

Hi Nick,

Your emails contain html and are not being archived by lore.kernel.org
or by marc.info.  Please fix that (no html) and resend the patch.

I don't know the answer to your question.  I would expect that whoever
merged the current drivers/platform/chrome/wilco_ec/ source files
could/would just take the new Kconfig patch and merge it also.


-- 
~Randy


Re: linux-next: Tree for Feb 12 (chrome/wilco_ec/)

2019-02-12 Thread Randy Dunlap
On 2/12/19 3:26 PM, Nick Crews wrote:
> Hi Randy,
> 
> This looks like we have a bad dependency structure in our Kconfig. I'll 
> figure it out, and then where should I send the patch?

AFAICT, all drivers/platform/chrome/ patches go to its maintainers (& to
linux-kernel@vger.kernel.org):

CHROME HARDWARE PLATFORM SUPPORT
M:  Benson Leung 
M:  Enric Balletbo i Serra 
S:  Maintained
T:  git 
git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git
F:  drivers/platform/chrome/


> Nick
> 
> On Tue, Feb 12, 2019 at 9:44 AM Randy Dunlap  > wrote:
> 
> On 2/11/19 10:50 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190211:
> >
> 
> 
> on i386 or x86_64:
> 
> ld: drivers/platform/chrome/wilco_ec/core.o: in function 
> `wilco_ec_remove':
> core.c:(.text+0x46): undefined reference to `cros_ec_lpc_mec_destroy'
> ld: drivers/platform/chrome/wilco_ec/core.o: in function `wilco_ec_probe':
> core.c:(.text+0x285): undefined reference to `cros_ec_lpc_mec_init'
> ld: core.c:(.text+0x39a): undefined reference to `cros_ec_lpc_mec_destroy'
> ld: drivers/platform/chrome/wilco_ec/mailbox.o: in function 
> `wilco_ec_transfer':
> mailbox.c:(.text+0x26): undefined reference to `cros_ec_lpc_io_bytes_mec'
> ld: mailbox.c:(.text+0x47): undefined reference to 
> `cros_ec_lpc_io_bytes_mec'
> ld: mailbox.c:(.text+0x242): undefined reference to 
> `cros_ec_lpc_io_bytes_mec'
> 
> 
> Full randconfig file is attached.
> 
> -- 
> ~Randy
> 


-- 
~Randy


Re: linux-next: Tree for Feb 12 (chrome/wilco_ec/)

2019-02-12 Thread Randy Dunlap
On 2/11/19 10:50 PM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20190211:
> 


on i386 or x86_64:

ld: drivers/platform/chrome/wilco_ec/core.o: in function `wilco_ec_remove':
core.c:(.text+0x46): undefined reference to `cros_ec_lpc_mec_destroy'
ld: drivers/platform/chrome/wilco_ec/core.o: in function `wilco_ec_probe':
core.c:(.text+0x285): undefined reference to `cros_ec_lpc_mec_init'
ld: core.c:(.text+0x39a): undefined reference to `cros_ec_lpc_mec_destroy'
ld: drivers/platform/chrome/wilco_ec/mailbox.o: in function `wilco_ec_transfer':
mailbox.c:(.text+0x26): undefined reference to `cros_ec_lpc_io_bytes_mec'
ld: mailbox.c:(.text+0x47): undefined reference to `cros_ec_lpc_io_bytes_mec'
ld: mailbox.c:(.text+0x242): undefined reference to `cros_ec_lpc_io_bytes_mec'


Full randconfig file is attached.

-- 
~Randy
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 5.0.0-rc6 Kernel Configuration
#

#
# Compiler: gcc (SUSE Linux) 4.8.5
#
CONFIG_CC_IS_GCC=y
CONFIG_GCC_VERSION=40805
CONFIG_CLANG_VERSION=0
CONFIG_CC_HAS_ASM_GOTO=y
CONFIG_CONSTRUCTORS=y
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y
CONFIG_THREAD_INFO_IN_TASK=y

#
# General setup
#
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_BUILD_SALT=""
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
# CONFIG_KERNEL_GZIP is not set
CONFIG_KERNEL_BZIP2=y
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
CONFIG_DEFAULT_HOSTNAME="(none)"
# CONFIG_SYSVIPC is not set
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_USELIB=y
CONFIG_AUDIT=y
CONFIG_HAVE_ARCH_AUDITSYSCALL=y
CONFIG_AUDITSYSCALL=y

#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_IRQ_CHIP=y
CONFIG_IRQ_DOMAIN=y
CONFIG_IRQ_SIM=y
CONFIG_IRQ_DOMAIN_HIERARCHY=y
CONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=y
CONFIG_GENERIC_IRQ_RESERVATION_MODE=y
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_GENERIC_IRQ_DEBUGFS=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_ARCH_CLOCKSOURCE_DATA=y
CONFIG_ARCH_CLOCKSOURCE_INIT=y
CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
CONFIG_GENERIC_CMOS_UPDATE=y

#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
CONFIG_NO_HZ_IDLE=y
CONFIG_NO_HZ=y
# CONFIG_HIGH_RES_TIMERS is not set
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set

#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
CONFIG_IRQ_TIME_ACCOUNTING=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_TASKSTATS=y
# CONFIG_TASK_DELAY_ACCT is not set
CONFIG_TASK_XACCT=y
# CONFIG_TASK_IO_ACCOUNTING is not set
CONFIG_PSI=y
CONFIG_PSI_DEFAULT_DISABLED=y

#
# RCU Subsystem
#
CONFIG_TINY_RCU=y
CONFIG_RCU_EXPERT=y
CONFIG_SRCU=y
CONFIG_TINY_SRCU=y
CONFIG_TASKS_RCU=y
CONFIG_BUILD_BIN2C=y
CONFIG_IKCONFIG=y
# CONFIG_IKCONFIG_PROC is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y
CONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH=y
CONFIG_ARCH_SUPPORTS_INT128=y
# CONFIG_CGROUPS is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
CONFIG_NET_NS=y
# CONFIG_CHECKPOINT_RESTORE is not set
# CONFIG_SCHED_AUTOGROUP is not set
# CONFIG_SYSFS_DEPRECATED is not set
CONFIG_RELAY=y
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
CONFIG_HAVE_UID16=y
CONFIG_SYSCTL_EXCEPTION_TRACE=y
CONFIG_HAVE_PCSPKR_PLATFORM=y
CONFIG_BPF=y
CONFIG_EXPERT=y
# CONFIG_UID16 is not set
CONFIG_MULTIUSER=y
# CONFIG_SGETMASK_SYSCALL is not set
CONFIG_SYSFS_SYSCALL=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_FHANDLE=y
CONFIG_POSIX_TIMERS=y
CONFIG_PRINTK=y
CONFIG_PRINTK_NMI=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
# CONFIG_PCSPKR_PLATFORM is not set
CONFIG_BASE_FULL=y
# CONFIG_FUTEX is not set
# CONFIG_EPOLL is not set
# CONFIG_SIGNALFD is not set
# CONFIG_TIMERFD is not set
# CONFIG_EVENTFD is not set
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_ADVISE_SYSCALLS=y
CONFIG_MEMBARRIER=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_BASE_RELATIVE=y
# CONFIG_BPF_SYSCALL is not set
# CONFIG_USERFAULTFD is not set
CONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=y
# CONFIG_RSEQ is not set
# CONFIG_EMBEDDED is not set
CONFIG_HAVE_PERF_EVENTS=y
CONFIG_PERF_USE_VMALLOC=y
# CONFIG_PC104 is not set

#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y

linux-next: Tree for Feb 12

2019-02-11 Thread Stephen Rothwell
Hi all,

Changes since 20190211:

The tegra tree gained a conflict against the imx-mxs tree.

The net-next tree gained a conflict against the net tree.

The drm-misc tree lost its build failure.

The rtc tree lost its build failure.

The xarray tree gained a build failure for which I added a merge fix
patch.

The akpm tree gained a conflict against the bpf tree.

Non-merge commits (relative to Linus' tree): 7147
 7676 files changed, 298091 insertions(+), 188993 deletions(-)



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log
files in the Next directory.  Between each merge, the tree was built
with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
multi_v7_defconfig for arm and a native build of tools/perf. After
the final fixups (if any), I do an x86_64 modules_install followed by
builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
and sparc64 defconfig. And finally, a simple boot test of the powerpc
pseries_le_defconfig kernel in qemu (with and without kvm enabled).

Below is a summary of the state of the merge.

I am currently merging 296 trees (counting Linus' and 69 trees of bug
fix patches pending for the current merge release).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

-- 
Cheers,
Stephen Rothwell

$ git checkout master
$ git reset --hard stable
Merging origin/master (fb7453e61a2b Merge tag 's390-5.0-3' of 
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux)
Merging fixes/master (0dd62c042779 x86/syscalls: Mark expected switch 
fall-throughs)
Merging kbuild-current/fixes (6db2983cd806 kallsyms: Handle too long symbols in 
kallsyms.c)
Merging arc-current/for-curr (a50d1c471ec5 ARC: boot: robustify u-boot arg 
referencing)
Merging arm-current/fixes (1b5ba3507842 ARM: 8824/1: fix a migrating irq bug 
when hotplug cpu)
Merging arm64-fixes/for-next/fixes (ea5736805190 arm64: kexec_file: handle 
empty command-line)
Merging m68k-current/for-linus (bed1369f5190 m68k: Fix memblock-related crashes)
Merging powerpc-fixes/fixes (5a3840a470c4 powerpc/papr_scm: Use the correct 
bind address)
Merging sparc/master (b71acb0e3721 Merge branch 'linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6)
Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2)
Merging net/master (4d73eaee24ff Merge 
git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf)
Merging bpf/master (e451eb510684 xsk: share the mmap_sem for page pinning)
Merging ipsec/master (f75a2804da39 xfrm: destroy xfrm_state synchronously on 
net exit path)
Merging netfilter/master (8303b7e8f018 netfilter: nat: fix spurious connection 
timeouts)
Merging ipvs/master (b2e3d68d1251 netfilter: nft_compat: destroy function must 
not have side effects)
Merging wireless-drivers/master (d04ca383860b mt76x0u: fix suspend/resume)
Merging mac80211/master (6157ca0d6bfe mac80211: Fix Tx aggregation session tear 
down with ITXQs)
Merging rdma-fixes/for-rc (48396e80fb65 RDMA/srp: Rework SCSI device reset 
handling)
Merging sound-current/for-linus (00a399cad1a0 ALSA: pcm: Revert capture stream 
behavior change in blocking mode)
Merging sound-asoc-fixes/for-linus (bb62989dccca Merge branch 'asoc-5.0' into 
asoc-linus)
Merging regmap-fixes/for-linus (f17b5f06cb92 Linux 5.0-rc4)
Merging regulator-fixes/for-linus (a71f59222522 Merge branch 'regulator-5.0' 
into regulator-linus)
Merging spi-fixes/for-linus (a4a9ebe8cb0f Merge branch 'spi-5.0' into spi-linus)
Merging pci-current/for-linus (f57a98e1b713 PCI: Work around Synopsys duplicate 
Device ID (HAPS USB3, NXP i.MX))
Merging driver-core.current/driver-core-linus (d13937116f1e Linux 5.0-rc6)
Merging tty.current/tty-linus (d13937116f1e Linux 5.0-rc6)
Merging usb.current/usb-linus (d13937116f1e Linux 5.0-rc6)
Merging usb-gadget-fixes/fixes (a53469a68eb8 usb: phy: am335x: fix race 
condition in _probe)
Merging usb-serial-fixes/usb-linus (dd9d3d86b08d USB: serial: cp210x: add ID 
for Ingenico 3070)
Merging usb-chipidea-fixes/ci-for-usb-stable (d6d768a0ec3c usb: chipidea: fix 
static 

linux-next: Tree for Feb 12

2018-02-11 Thread Stephen Rothwell
Hi all,

Changes since 20180209:

The btrfs-kdave tree lost its build failure.

The tip tree gained a conflict against Linus' tree.

Non-merge commits (relative to Linus' tree): 422
 451 files changed, 15667 insertions(+), 3551 deletions(-)



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log
files in the Next directory.  Between each merge, the tree was built
with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
multi_v7_defconfig for arm and a native build of tools/perf. After
the final fixups (if any), I do an x86_64 modules_install followed by
builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
and sparc64 defconfig. And finally, a simple boot test of the powerpc
pseries_le_defconfig kernel in qemu (with and without kvm enabled).

Below is a summary of the state of the merge.

I am currently merging 256 trees (counting Linus' and 44 trees of bug
fix patches pending for the current merge release).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

-- 
Cheers,
Stephen Rothwell

$ git checkout master
$ git reset --hard stable
Merging origin/master (7928b2cbe55b Linux 4.16-rc1)
Merging fixes/master (7928b2cbe55b Linux 4.16-rc1)
Merging kbuild-current/fixes (36c1681678b5 genksyms: drop *.hash.c from 
.gitignore)
Merging arc-current/for-curr (053823335956 arc: dts: use 'atmel' as 
manufacturer for at24 in axs10x_mb)
Merging arm-current/fixes (091f02483df7 ARM: net: bpf: clarify tail_call index)
Merging m68k-current/for-linus (2334b1ac1235 MAINTAINERS: Add NuBus subsystem 
entry)
Merging metag-fixes/fixes (b884a190afce metag/usercopy: Add missing fixups)
Merging powerpc-fixes/fixes (4dd5f8a99e79 powerpc/mm/radix: Split linear 
mapping on hot-unplug)
Merging sparc/master (aebb48f5e465 sparc64: fix typo in 
CONFIG_CRYPTO_DES_SPARC64 => CONFIG_CRYPTO_CAMELLIA_SPARC64)
Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2)
Merging net/master (9a61df9e5f74 Merge tag 'kbuild-v4.16-2' of 
git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild)
Merging bpf/master (d977ae593b2d Merge branch 'bpf-libbpf-relo-fix-and-tests')
Merging ipsec/master (545d8ae7afff xfrm: fix boolean assignment in 
xfrm_get_type_offload)
Merging netfilter/master (fd2c19b2a28b netfilter: x_tables: remove size check)
Merging ipvs/master (f7fb77fc1235 netfilter: nft_compat: check extension hook 
mask only if set)
Merging wireless-drivers/master (08f513851218 net: phy: fix phy_start to 
consider PHY_IGNORE_INTERRUPT)
Merging mac80211/master (c4de37ee2b55 mac80211: mesh: fix wrong mesh TTL offset 
calculation)
Merging rdma-fixes/for-rc (ae59c3f0b6cf RDMA/mlx5: Fix out-of-bound access 
while querying AH)
Merging sound-current/for-linus (61fcf8ece9b6 ALSA: hda/realtek - Enable 
Thinkpad Dock device for ALC298 platform)
Merging pci-current/for-linus (c591c2e36ccc powerpc/pci: Fix broken INTx 
configuration via OF)
Merging driver-core.current/driver-core-linus (f1517df8701c Merge tag 
'nfsd-4.16' of git://linux-nfs.org/~bfields/linux)
Merging tty.current/tty-linus (f1517df8701c Merge tag 'nfsd-4.16' of 
git://linux-nfs.org/~bfields/linux)
Merging usb.current/usb-linus (f1517df8701c Merge tag 'nfsd-4.16' of 
git://linux-nfs.org/~bfields/linux)
Merging usb-gadget-fixes/fixes (b2cd1df66037 Linux 4.15-rc7)
Merging usb-serial-fixes/usb-linus (d14ac576d10f USB: serial: cp210x: add new 
device ID ELV ALC 8xxx)
Merging usb-chipidea-fixes/ci-for-usb-stable (964728f9f407 USB: chipidea: msm: 
fix ulpi-node lookup)
Merging phy/fixes (2b88212c4cc6 phy: rcar-gen3-usb2: select USB_COMMON)
Merging staging.current/staging-linus (f1517df8701c Merge tag 'nfsd-4.16' of 
git://linux-nfs.org/~bfields/linux)
Merging char-misc.current/char-misc-linus (f1517df8701c Merge tag 'nfsd-4.16' 
of git://linux-nfs.org/~bfields/linux)
Merging input-current/for-linus (ea4f7bd2aca9 Input: matrix_keypad - fix race 
when disabling interrupts)
Merging crypto-current/master (2e7d1d61ea6c crypto: sun4i_ss_prng - convert 
lock to _bh in sun4i_ss_prng_generate)

linux-next: Tree for Feb 12

2018-02-11 Thread Stephen Rothwell
Hi all,

Changes since 20180209:

The btrfs-kdave tree lost its build failure.

The tip tree gained a conflict against Linus' tree.

Non-merge commits (relative to Linus' tree): 422
 451 files changed, 15667 insertions(+), 3551 deletions(-)



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log
files in the Next directory.  Between each merge, the tree was built
with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
multi_v7_defconfig for arm and a native build of tools/perf. After
the final fixups (if any), I do an x86_64 modules_install followed by
builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
and sparc64 defconfig. And finally, a simple boot test of the powerpc
pseries_le_defconfig kernel in qemu (with and without kvm enabled).

Below is a summary of the state of the merge.

I am currently merging 256 trees (counting Linus' and 44 trees of bug
fix patches pending for the current merge release).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

-- 
Cheers,
Stephen Rothwell

$ git checkout master
$ git reset --hard stable
Merging origin/master (7928b2cbe55b Linux 4.16-rc1)
Merging fixes/master (7928b2cbe55b Linux 4.16-rc1)
Merging kbuild-current/fixes (36c1681678b5 genksyms: drop *.hash.c from 
.gitignore)
Merging arc-current/for-curr (053823335956 arc: dts: use 'atmel' as 
manufacturer for at24 in axs10x_mb)
Merging arm-current/fixes (091f02483df7 ARM: net: bpf: clarify tail_call index)
Merging m68k-current/for-linus (2334b1ac1235 MAINTAINERS: Add NuBus subsystem 
entry)
Merging metag-fixes/fixes (b884a190afce metag/usercopy: Add missing fixups)
Merging powerpc-fixes/fixes (4dd5f8a99e79 powerpc/mm/radix: Split linear 
mapping on hot-unplug)
Merging sparc/master (aebb48f5e465 sparc64: fix typo in 
CONFIG_CRYPTO_DES_SPARC64 => CONFIG_CRYPTO_CAMELLIA_SPARC64)
Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2)
Merging net/master (9a61df9e5f74 Merge tag 'kbuild-v4.16-2' of 
git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild)
Merging bpf/master (d977ae593b2d Merge branch 'bpf-libbpf-relo-fix-and-tests')
Merging ipsec/master (545d8ae7afff xfrm: fix boolean assignment in 
xfrm_get_type_offload)
Merging netfilter/master (fd2c19b2a28b netfilter: x_tables: remove size check)
Merging ipvs/master (f7fb77fc1235 netfilter: nft_compat: check extension hook 
mask only if set)
Merging wireless-drivers/master (08f513851218 net: phy: fix phy_start to 
consider PHY_IGNORE_INTERRUPT)
Merging mac80211/master (c4de37ee2b55 mac80211: mesh: fix wrong mesh TTL offset 
calculation)
Merging rdma-fixes/for-rc (ae59c3f0b6cf RDMA/mlx5: Fix out-of-bound access 
while querying AH)
Merging sound-current/for-linus (61fcf8ece9b6 ALSA: hda/realtek - Enable 
Thinkpad Dock device for ALC298 platform)
Merging pci-current/for-linus (c591c2e36ccc powerpc/pci: Fix broken INTx 
configuration via OF)
Merging driver-core.current/driver-core-linus (f1517df8701c Merge tag 
'nfsd-4.16' of git://linux-nfs.org/~bfields/linux)
Merging tty.current/tty-linus (f1517df8701c Merge tag 'nfsd-4.16' of 
git://linux-nfs.org/~bfields/linux)
Merging usb.current/usb-linus (f1517df8701c Merge tag 'nfsd-4.16' of 
git://linux-nfs.org/~bfields/linux)
Merging usb-gadget-fixes/fixes (b2cd1df66037 Linux 4.15-rc7)
Merging usb-serial-fixes/usb-linus (d14ac576d10f USB: serial: cp210x: add new 
device ID ELV ALC 8xxx)
Merging usb-chipidea-fixes/ci-for-usb-stable (964728f9f407 USB: chipidea: msm: 
fix ulpi-node lookup)
Merging phy/fixes (2b88212c4cc6 phy: rcar-gen3-usb2: select USB_COMMON)
Merging staging.current/staging-linus (f1517df8701c Merge tag 'nfsd-4.16' of 
git://linux-nfs.org/~bfields/linux)
Merging char-misc.current/char-misc-linus (f1517df8701c Merge tag 'nfsd-4.16' 
of git://linux-nfs.org/~bfields/linux)
Merging input-current/for-linus (ea4f7bd2aca9 Input: matrix_keypad - fix race 
when disabling interrupts)
Merging crypto-current/master (2e7d1d61ea6c crypto: sun4i_ss_prng - convert 
lock to _bh in sun4i_ss_prng_generate)

Re: linux-next: Tree for Feb 12

2016-02-13 Thread Sudip Mukherjee

On Saturday 13 February 2016 09:20 PM, Borislav Petkov wrote:

On Sat, Feb 13, 2016 at 06:57:24AM -0800, Andy Lutomirski wrote:

I think Borislav's patch should fix this.


Yeah, guys, can you give it a try:

https://lkml.kernel.org/r/20160210145116.gf23...@pd.tnic


Its late night in our time so I could only test with i386 defconfig and 
it builds fine with gcc-4.6.3


regards
sudip


Re: linux-next: Tree for Feb 12

2016-02-13 Thread Borislav Petkov
On Sat, Feb 13, 2016 at 06:57:24AM -0800, Andy Lutomirski wrote:
> I think Borislav's patch should fix this.

Yeah, guys, can you give it a try:

https://lkml.kernel.org/r/20160210145116.gf23...@pd.tnic

Thanks.

-- 
Regards/Gruss,
Boris.

ECO tip #101: Trim your mails when you reply.


Re: linux-next: Tree for Feb 12

2016-02-13 Thread Andy Lutomirski
On Fri, Feb 12, 2016 at 11:49 PM, Guenter Roeck  wrote:
> On Fri, Feb 12, 2016 at 11:32:42AM +0530, Sudip Mukherjee wrote:
>> On Fri, Feb 12, 2016 at 04:20:35PM +1100, Stephen Rothwell wrote:
>> > Hi all,
>> >
>> > Changes since 20160211:
>>
>> since last few days with gcc-4.6.3, x86_64 and i386 defconfig and
>> allmodconfig builds are failing with the error:
>> "arch/x86/include/asm/tlbflush.h:26:18: error: memory input 0 is not
>> directly addressable"
>>
>> But with gcc-4.8.2 and later it builds fine. Should I try to bisect and
>> find the problem or its not worth for gcc-4.6.3 ?
>>
> Bisect log attached. Looks like older versions of gcc (or at least 4.6.3)
> don't like the newly introduced __invpcid().
>
> Guenter
>
> ---
> # bad: [64d9a3617b3b8bc0734ba97caeb433b7019c6187] Add linux-next specific 
> files for 20160212
> # good: [388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95] Linux 4.5-rc3
> git bisect start 'HEAD' 'v4.5-rc3'
> # good: [597dc9d36e8bc04941b61b26ac7aa3f8a33aba53] Merge remote-tracking 
> branch 'sound-asoc/for-next'
> git bisect good 597dc9d36e8bc04941b61b26ac7aa3f8a33aba53
> # bad: [91fe8ea815243ec595753ccf7e14126b6f87f2bf] Merge remote-tracking 
> branch 'usb-chipidea-next/ci-for-usb-next'
> git bisect bad 91fe8ea815243ec595753ccf7e14126b6f87f2bf
> # bad: [1d6796e67f265e835bcb1a19d27ba0433dbd75e4] Merge remote-tracking 
> branch 'tip/auto-latest'
> git bisect bad 1d6796e67f265e835bcb1a19d27ba0433dbd75e4
> # good: [4abecd5aab4960c786530db5ce4ca332ceba2b73] Merge branch 
> 'x86/microcode'
> git bisect good 4abecd5aab4960c786530db5ce4ca332ceba2b73
> # good: [84d5092d655bc9532c5fc88e7b2308090889187d] Merge remote-tracking 
> branch 'kgdb/kgdb-next'
> git bisect good 84d5092d655bc9532c5fc88e7b2308090889187d
> # good: [e4e0cfcfc9fd3885ff7dadfb5a4b553495d011e4] Merge remote-tracking 
> branch 'iommu/next'
> git bisect good e4e0cfcfc9fd3885ff7dadfb5a4b553495d011e4
> # good: [e908e75fc3833b413837aca4667db96c372c843e] Merge remote-tracking 
> branch 'spi/topic/ti-qspi' into spi-next
> git bisect good e908e75fc3833b413837aca4667db96c372c843e
> # good: [88e2211191dabe9ae2a953d5a4326d3e4b7f2901] Merge remote-tracking 
> branch 'trivial/for-next'
> git bisect good 88e2211191dabe9ae2a953d5a4326d3e4b7f2901
> # good: [d12a72b844a49d4162f24cefdab30bed3f86730e] x86/mm: Add a 'noinvpcid' 
> boot option to turn off INVPCID
> git bisect good d12a72b844a49d4162f24cefdab30bed3f86730e
> # good: [a135746b7d4386c17290e030101d037e86f8] Merge remote-tracking 
> branch 'dt-rh/for-next'
> git bisect good a135746b7d4386c17290e030101d037e86f8
> # bad: [ce1143aa60273220a9f89012f2aaaed04f97e9a2] x86/dmi: Switch dmi_remap() 
> from ioremap() [uncached] to ioremap_cache()
> git bisect bad ce1143aa60273220a9f89012f2aaaed04f97e9a2
> # bad: [d8bced79af1db6734f66b42064cc773cada2ce99] x86/mm: If INVPCID is 
> available, use it to flush global mappings
> git bisect bad d8bced79af1db6734f66b42064cc773cada2ce99
> # first bad commit: [d8bced79af1db6734f66b42064cc773cada2ce99] x86/mm: If 
> INVPCID is available, use it to flush global mappings

I think Borislav's patch should fix this.

--Andy

-- 
Andy Lutomirski
AMA Capital Management, LLC


Re: linux-next: Tree for Feb 12

2016-02-13 Thread Andy Lutomirski
On Fri, Feb 12, 2016 at 11:49 PM, Guenter Roeck  wrote:
> On Fri, Feb 12, 2016 at 11:32:42AM +0530, Sudip Mukherjee wrote:
>> On Fri, Feb 12, 2016 at 04:20:35PM +1100, Stephen Rothwell wrote:
>> > Hi all,
>> >
>> > Changes since 20160211:
>>
>> since last few days with gcc-4.6.3, x86_64 and i386 defconfig and
>> allmodconfig builds are failing with the error:
>> "arch/x86/include/asm/tlbflush.h:26:18: error: memory input 0 is not
>> directly addressable"
>>
>> But with gcc-4.8.2 and later it builds fine. Should I try to bisect and
>> find the problem or its not worth for gcc-4.6.3 ?
>>
> Bisect log attached. Looks like older versions of gcc (or at least 4.6.3)
> don't like the newly introduced __invpcid().
>
> Guenter
>
> ---
> # bad: [64d9a3617b3b8bc0734ba97caeb433b7019c6187] Add linux-next specific 
> files for 20160212
> # good: [388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95] Linux 4.5-rc3
> git bisect start 'HEAD' 'v4.5-rc3'
> # good: [597dc9d36e8bc04941b61b26ac7aa3f8a33aba53] Merge remote-tracking 
> branch 'sound-asoc/for-next'
> git bisect good 597dc9d36e8bc04941b61b26ac7aa3f8a33aba53
> # bad: [91fe8ea815243ec595753ccf7e14126b6f87f2bf] Merge remote-tracking 
> branch 'usb-chipidea-next/ci-for-usb-next'
> git bisect bad 91fe8ea815243ec595753ccf7e14126b6f87f2bf
> # bad: [1d6796e67f265e835bcb1a19d27ba0433dbd75e4] Merge remote-tracking 
> branch 'tip/auto-latest'
> git bisect bad 1d6796e67f265e835bcb1a19d27ba0433dbd75e4
> # good: [4abecd5aab4960c786530db5ce4ca332ceba2b73] Merge branch 
> 'x86/microcode'
> git bisect good 4abecd5aab4960c786530db5ce4ca332ceba2b73
> # good: [84d5092d655bc9532c5fc88e7b2308090889187d] Merge remote-tracking 
> branch 'kgdb/kgdb-next'
> git bisect good 84d5092d655bc9532c5fc88e7b2308090889187d
> # good: [e4e0cfcfc9fd3885ff7dadfb5a4b553495d011e4] Merge remote-tracking 
> branch 'iommu/next'
> git bisect good e4e0cfcfc9fd3885ff7dadfb5a4b553495d011e4
> # good: [e908e75fc3833b413837aca4667db96c372c843e] Merge remote-tracking 
> branch 'spi/topic/ti-qspi' into spi-next
> git bisect good e908e75fc3833b413837aca4667db96c372c843e
> # good: [88e2211191dabe9ae2a953d5a4326d3e4b7f2901] Merge remote-tracking 
> branch 'trivial/for-next'
> git bisect good 88e2211191dabe9ae2a953d5a4326d3e4b7f2901
> # good: [d12a72b844a49d4162f24cefdab30bed3f86730e] x86/mm: Add a 'noinvpcid' 
> boot option to turn off INVPCID
> git bisect good d12a72b844a49d4162f24cefdab30bed3f86730e
> # good: [a135746b7d4386c17290e030101d037e86f8] Merge remote-tracking 
> branch 'dt-rh/for-next'
> git bisect good a135746b7d4386c17290e030101d037e86f8
> # bad: [ce1143aa60273220a9f89012f2aaaed04f97e9a2] x86/dmi: Switch dmi_remap() 
> from ioremap() [uncached] to ioremap_cache()
> git bisect bad ce1143aa60273220a9f89012f2aaaed04f97e9a2
> # bad: [d8bced79af1db6734f66b42064cc773cada2ce99] x86/mm: If INVPCID is 
> available, use it to flush global mappings
> git bisect bad d8bced79af1db6734f66b42064cc773cada2ce99
> # first bad commit: [d8bced79af1db6734f66b42064cc773cada2ce99] x86/mm: If 
> INVPCID is available, use it to flush global mappings

I think Borislav's patch should fix this.

--Andy

-- 
Andy Lutomirski
AMA Capital Management, LLC


Re: linux-next: Tree for Feb 12

2016-02-13 Thread Borislav Petkov
On Sat, Feb 13, 2016 at 06:57:24AM -0800, Andy Lutomirski wrote:
> I think Borislav's patch should fix this.

Yeah, guys, can you give it a try:

https://lkml.kernel.org/r/20160210145116.gf23...@pd.tnic

Thanks.

-- 
Regards/Gruss,
Boris.

ECO tip #101: Trim your mails when you reply.


Re: linux-next: Tree for Feb 12

2016-02-13 Thread Sudip Mukherjee

On Saturday 13 February 2016 09:20 PM, Borislav Petkov wrote:

On Sat, Feb 13, 2016 at 06:57:24AM -0800, Andy Lutomirski wrote:

I think Borislav's patch should fix this.


Yeah, guys, can you give it a try:

https://lkml.kernel.org/r/20160210145116.gf23...@pd.tnic


Its late night in our time so I could only test with i386 defconfig and 
it builds fine with gcc-4.6.3


regards
sudip


Re: linux-next: Tree for Feb 12

2016-02-12 Thread Guenter Roeck
On Fri, Feb 12, 2016 at 11:32:42AM +0530, Sudip Mukherjee wrote:
> On Fri, Feb 12, 2016 at 04:20:35PM +1100, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20160211:
> 
> since last few days with gcc-4.6.3, x86_64 and i386 defconfig and
> allmodconfig builds are failing with the error:
> "arch/x86/include/asm/tlbflush.h:26:18: error: memory input 0 is not
> directly addressable"
> 
> But with gcc-4.8.2 and later it builds fine. Should I try to bisect and
> find the problem or its not worth for gcc-4.6.3 ?
> 
Bisect log attached. Looks like older versions of gcc (or at least 4.6.3)
don't like the newly introduced __invpcid().

Guenter

---
# bad: [64d9a3617b3b8bc0734ba97caeb433b7019c6187] Add linux-next specific files 
for 20160212
# good: [388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95] Linux 4.5-rc3
git bisect start 'HEAD' 'v4.5-rc3'
# good: [597dc9d36e8bc04941b61b26ac7aa3f8a33aba53] Merge remote-tracking branch 
'sound-asoc/for-next'
git bisect good 597dc9d36e8bc04941b61b26ac7aa3f8a33aba53
# bad: [91fe8ea815243ec595753ccf7e14126b6f87f2bf] Merge remote-tracking branch 
'usb-chipidea-next/ci-for-usb-next'
git bisect bad 91fe8ea815243ec595753ccf7e14126b6f87f2bf
# bad: [1d6796e67f265e835bcb1a19d27ba0433dbd75e4] Merge remote-tracking branch 
'tip/auto-latest'
git bisect bad 1d6796e67f265e835bcb1a19d27ba0433dbd75e4
# good: [4abecd5aab4960c786530db5ce4ca332ceba2b73] Merge branch 'x86/microcode'
git bisect good 4abecd5aab4960c786530db5ce4ca332ceba2b73
# good: [84d5092d655bc9532c5fc88e7b2308090889187d] Merge remote-tracking branch 
'kgdb/kgdb-next'
git bisect good 84d5092d655bc9532c5fc88e7b2308090889187d
# good: [e4e0cfcfc9fd3885ff7dadfb5a4b553495d011e4] Merge remote-tracking branch 
'iommu/next'
git bisect good e4e0cfcfc9fd3885ff7dadfb5a4b553495d011e4
# good: [e908e75fc3833b413837aca4667db96c372c843e] Merge remote-tracking branch 
'spi/topic/ti-qspi' into spi-next
git bisect good e908e75fc3833b413837aca4667db96c372c843e
# good: [88e2211191dabe9ae2a953d5a4326d3e4b7f2901] Merge remote-tracking branch 
'trivial/for-next'
git bisect good 88e2211191dabe9ae2a953d5a4326d3e4b7f2901
# good: [d12a72b844a49d4162f24cefdab30bed3f86730e] x86/mm: Add a 'noinvpcid' 
boot option to turn off INVPCID
git bisect good d12a72b844a49d4162f24cefdab30bed3f86730e
# good: [a135746b7d4386c17290e030101d037e86f8] Merge remote-tracking branch 
'dt-rh/for-next'
git bisect good a135746b7d4386c17290e030101d037e86f8
# bad: [ce1143aa60273220a9f89012f2aaaed04f97e9a2] x86/dmi: Switch dmi_remap() 
from ioremap() [uncached] to ioremap_cache()
git bisect bad ce1143aa60273220a9f89012f2aaaed04f97e9a2
# bad: [d8bced79af1db6734f66b42064cc773cada2ce99] x86/mm: If INVPCID is 
available, use it to flush global mappings
git bisect bad d8bced79af1db6734f66b42064cc773cada2ce99
# first bad commit: [d8bced79af1db6734f66b42064cc773cada2ce99] x86/mm: If 
INVPCID is available, use it to flush global mappings


Re: linux-next: Tree for Feb 12

2016-02-12 Thread Sudip Mukherjee
On Fri, Feb 12, 2016 at 04:20:35PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20160211:

arm lpc18xx_defconfig build fails with the error:
./arch/arm/kernel/vmlinux.lds:702: undefined symbol `SECTION_SHIFT'
referenced in expression

bisect leads to:
64ac2e74f0b2 ("ARM: 8502/1: mm: mark section-aligned portion of rodata NX")

reverting that patch fixed the build.

build log at:
https://travis-ci.org/sudipm-mukherjee/parport/jobs/108716281

regards
sudip


Re: linux-next: Tree for Feb 12

2016-02-12 Thread Sudip Mukherjee
On Fri, Feb 12, 2016 at 04:20:35PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20160211:

arm lpc18xx_defconfig build fails with the error:
./arch/arm/kernel/vmlinux.lds:702: undefined symbol `SECTION_SHIFT'
referenced in expression

bisect leads to:
64ac2e74f0b2 ("ARM: 8502/1: mm: mark section-aligned portion of rodata NX")

reverting that patch fixed the build.

build log at:
https://travis-ci.org/sudipm-mukherjee/parport/jobs/108716281

regards
sudip


Re: linux-next: Tree for Feb 12

2016-02-12 Thread Guenter Roeck
On Fri, Feb 12, 2016 at 11:32:42AM +0530, Sudip Mukherjee wrote:
> On Fri, Feb 12, 2016 at 04:20:35PM +1100, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20160211:
> 
> since last few days with gcc-4.6.3, x86_64 and i386 defconfig and
> allmodconfig builds are failing with the error:
> "arch/x86/include/asm/tlbflush.h:26:18: error: memory input 0 is not
> directly addressable"
> 
> But with gcc-4.8.2 and later it builds fine. Should I try to bisect and
> find the problem or its not worth for gcc-4.6.3 ?
> 
Bisect log attached. Looks like older versions of gcc (or at least 4.6.3)
don't like the newly introduced __invpcid().

Guenter

---
# bad: [64d9a3617b3b8bc0734ba97caeb433b7019c6187] Add linux-next specific files 
for 20160212
# good: [388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95] Linux 4.5-rc3
git bisect start 'HEAD' 'v4.5-rc3'
# good: [597dc9d36e8bc04941b61b26ac7aa3f8a33aba53] Merge remote-tracking branch 
'sound-asoc/for-next'
git bisect good 597dc9d36e8bc04941b61b26ac7aa3f8a33aba53
# bad: [91fe8ea815243ec595753ccf7e14126b6f87f2bf] Merge remote-tracking branch 
'usb-chipidea-next/ci-for-usb-next'
git bisect bad 91fe8ea815243ec595753ccf7e14126b6f87f2bf
# bad: [1d6796e67f265e835bcb1a19d27ba0433dbd75e4] Merge remote-tracking branch 
'tip/auto-latest'
git bisect bad 1d6796e67f265e835bcb1a19d27ba0433dbd75e4
# good: [4abecd5aab4960c786530db5ce4ca332ceba2b73] Merge branch 'x86/microcode'
git bisect good 4abecd5aab4960c786530db5ce4ca332ceba2b73
# good: [84d5092d655bc9532c5fc88e7b2308090889187d] Merge remote-tracking branch 
'kgdb/kgdb-next'
git bisect good 84d5092d655bc9532c5fc88e7b2308090889187d
# good: [e4e0cfcfc9fd3885ff7dadfb5a4b553495d011e4] Merge remote-tracking branch 
'iommu/next'
git bisect good e4e0cfcfc9fd3885ff7dadfb5a4b553495d011e4
# good: [e908e75fc3833b413837aca4667db96c372c843e] Merge remote-tracking branch 
'spi/topic/ti-qspi' into spi-next
git bisect good e908e75fc3833b413837aca4667db96c372c843e
# good: [88e2211191dabe9ae2a953d5a4326d3e4b7f2901] Merge remote-tracking branch 
'trivial/for-next'
git bisect good 88e2211191dabe9ae2a953d5a4326d3e4b7f2901
# good: [d12a72b844a49d4162f24cefdab30bed3f86730e] x86/mm: Add a 'noinvpcid' 
boot option to turn off INVPCID
git bisect good d12a72b844a49d4162f24cefdab30bed3f86730e
# good: [a135746b7d4386c17290e030101d037e86f8] Merge remote-tracking branch 
'dt-rh/for-next'
git bisect good a135746b7d4386c17290e030101d037e86f8
# bad: [ce1143aa60273220a9f89012f2aaaed04f97e9a2] x86/dmi: Switch dmi_remap() 
from ioremap() [uncached] to ioremap_cache()
git bisect bad ce1143aa60273220a9f89012f2aaaed04f97e9a2
# bad: [d8bced79af1db6734f66b42064cc773cada2ce99] x86/mm: If INVPCID is 
available, use it to flush global mappings
git bisect bad d8bced79af1db6734f66b42064cc773cada2ce99
# first bad commit: [d8bced79af1db6734f66b42064cc773cada2ce99] x86/mm: If 
INVPCID is available, use it to flush global mappings


Re: linux-next: Tree for Feb 12

2016-02-11 Thread Sudip Mukherjee
On Fri, Feb 12, 2016 at 04:20:35PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20160211:

since last few days with gcc-4.6.3, x86_64 and i386 defconfig and
allmodconfig builds are failing with the error:
"arch/x86/include/asm/tlbflush.h:26:18: error: memory input 0 is not
directly addressable"

But with gcc-4.8.2 and later it builds fine. Should I try to bisect and
find the problem or its not worth for gcc-4.6.3 ?

regards
sudip



linux-next: Tree for Feb 12

2016-02-11 Thread Stephen Rothwell
Hi all,

Changes since 20160211:

The kvm-arm tree gained a conflict against the arm64 tree.

The aio tree still had a build failure so I used the version from
next-20160111.

Non-merge commits (relative to Linus' tree): 4277
 3754 files changed, 149171 insertions(+), 67859 deletions(-)



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log
files in the Next directory.  Between each merge, the tree was built
with a ppc64_defconfig for powerpc and an allmodconfig (with
CONFIG_BUILD_DOCSRC=n) for x86_64, a multi_v7_defconfig for arm and a
native build of tools/perf. After the final fixups (if any), I do an
x86_64 modules_install followed by builds for x86_64 allnoconfig,
powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig
(this fails its final link) and pseries_le_defconfig and i386, sparc
and sparc64 defconfig.

Below is a summary of the state of the merge.

I am currently merging 239 trees (counting Linus' and 36 trees of patches
pending for Linus' tree).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

-- 
Cheers,
Stephen Rothwell

$ git checkout master
$ git reset --hard stable
Merging origin/master (c05235d50f68 Merge tag 'gpio-v4.5-2' of 
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio)
Merging fixes/master (36f90b0a2ddd Linux 4.5-rc2)
Merging kbuild-current/rc-fixes (3d1450d54a4f Makefile: Force gzip and xz on 
module install)
Merging arc-current/for-curr (74bf8efb5fa6 Linux 4.4-rc7)
Merging arm-current/fixes (e972c37459c8 ARM: 8519/1: ICST: try other dividends 
than 1)
Merging m68k-current/for-linus (daf670bc9d36 m68k/defconfig: Update defconfigs 
for v4.5-rc1)
Merging metag-fixes/fixes (0164a711c97b metag: Fix ioremap_wc/ioremap_cached 
build errors)
Merging mips-fixes/mips-fixes (1795cd9b3a91 Linux 3.16-rc5)
Merging powerpc-fixes/fixes (0fe53e8d335b powerpc/powernv: Fix stale PE primary 
bus)
Merging powerpc-merge-mpe/fixes (bc0195aad0da Linux 4.2-rc2)
Merging sparc/master (ca0bb0798022 Add sun4v_wdt watchdog driver)
Merging net/master (a1b14d27ed09 bpf: fix branch offset adjustment on backjumps 
after patching ctx expansion)
Merging ipsec/master (a8a572a6b5f2 xfrm: dst_entries_init() per-net dst_ops)
Merging ipvs/master (b16c29191dc8 netfilter: nf_conntrack: use safer way to 
lock all buckets)
Merging wireless-drivers/master (d76d65fd2695 rtlwifi: fix broken VHT support)
Merging mac80211/master (212c5a5e6ba6 mac80211: minstrel: Change expected 
throughput unit back to Kbps)
Merging sound-current/for-linus (397da2d0ab0d Merge branch 'topic/core-fixes' 
into for-linus)
Merging pci-current/for-linus (0cf1337e0b83 PCI: rcar: Add device tree support 
for r8a7793)
Merging driver-core.current/driver-core-linus (00cd29b799e3 klist: fix starting 
point removed bug in klist iterators)
Merging tty.current/tty-linus (c8053b587627 Revert "8250: uniphier: allow 
modular build with 8250 console")
Merging usb.current/usb-linus (89140fdaf11a xhci: harden xhci_find_next_ext_cap 
against device removal)
Merging usb-gadget-fixes/fixes (6a4290cc28be usb: dwc3: gadget: set the OTG 
flag in dwc3 gadget driver.)
Merging usb-serial-fixes/usb-linus (4152b387da81 USB: option: fix Cinterion 
AHxx enumeration)
Merging usb-chipidea-fixes/ci-for-usb-stable (6f51bc340d2a usb: chipidea: imx: 
fix a possible NULL dereference)
Merging staging.current/staging-linus (388f7b1d6e8c Linux 4.5-rc3)
Merging char-misc.current/char-misc-linus (3b2b9ead3214 nvmem: qfprom: Specify 
LE device endianness)
Merging input-current/for-linus (ff84dabe3c6e Input: colibri-vf50-ts - add 
missing #include )
Merging crypto-current/master (8a3978ad55fb crypto: marvell/cesa - fix test in 
mv_cesa_dev_dma_init())
Merging ide/master (e04a2bd6d8c9 drivers/ide: make ide-scan-pci.c driver 
explicitly non-modular)
Merging devicetree-current/devicetree/merge (f76502aa9140 of/dynamic: Fix test 
for PPC_PSERIES)
Merging rr-fixes/fixes (8244062ef1e5 modules: fix longstanding /proc/kallsyms 
vs module insertion race.)
Merging vfio-fixes/for-linus (16ab8a5cbea4 vfio/noiommu: Don't use 
iommu_present() to track fake groups)

linux-next: Tree for Feb 12

2016-02-11 Thread Stephen Rothwell
Hi all,

Changes since 20160211:

The kvm-arm tree gained a conflict against the arm64 tree.

The aio tree still had a build failure so I used the version from
next-20160111.

Non-merge commits (relative to Linus' tree): 4277
 3754 files changed, 149171 insertions(+), 67859 deletions(-)



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log
files in the Next directory.  Between each merge, the tree was built
with a ppc64_defconfig for powerpc and an allmodconfig (with
CONFIG_BUILD_DOCSRC=n) for x86_64, a multi_v7_defconfig for arm and a
native build of tools/perf. After the final fixups (if any), I do an
x86_64 modules_install followed by builds for x86_64 allnoconfig,
powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig
(this fails its final link) and pseries_le_defconfig and i386, sparc
and sparc64 defconfig.

Below is a summary of the state of the merge.

I am currently merging 239 trees (counting Linus' and 36 trees of patches
pending for Linus' tree).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

-- 
Cheers,
Stephen Rothwell

$ git checkout master
$ git reset --hard stable
Merging origin/master (c05235d50f68 Merge tag 'gpio-v4.5-2' of 
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio)
Merging fixes/master (36f90b0a2ddd Linux 4.5-rc2)
Merging kbuild-current/rc-fixes (3d1450d54a4f Makefile: Force gzip and xz on 
module install)
Merging arc-current/for-curr (74bf8efb5fa6 Linux 4.4-rc7)
Merging arm-current/fixes (e972c37459c8 ARM: 8519/1: ICST: try other dividends 
than 1)
Merging m68k-current/for-linus (daf670bc9d36 m68k/defconfig: Update defconfigs 
for v4.5-rc1)
Merging metag-fixes/fixes (0164a711c97b metag: Fix ioremap_wc/ioremap_cached 
build errors)
Merging mips-fixes/mips-fixes (1795cd9b3a91 Linux 3.16-rc5)
Merging powerpc-fixes/fixes (0fe53e8d335b powerpc/powernv: Fix stale PE primary 
bus)
Merging powerpc-merge-mpe/fixes (bc0195aad0da Linux 4.2-rc2)
Merging sparc/master (ca0bb0798022 Add sun4v_wdt watchdog driver)
Merging net/master (a1b14d27ed09 bpf: fix branch offset adjustment on backjumps 
after patching ctx expansion)
Merging ipsec/master (a8a572a6b5f2 xfrm: dst_entries_init() per-net dst_ops)
Merging ipvs/master (b16c29191dc8 netfilter: nf_conntrack: use safer way to 
lock all buckets)
Merging wireless-drivers/master (d76d65fd2695 rtlwifi: fix broken VHT support)
Merging mac80211/master (212c5a5e6ba6 mac80211: minstrel: Change expected 
throughput unit back to Kbps)
Merging sound-current/for-linus (397da2d0ab0d Merge branch 'topic/core-fixes' 
into for-linus)
Merging pci-current/for-linus (0cf1337e0b83 PCI: rcar: Add device tree support 
for r8a7793)
Merging driver-core.current/driver-core-linus (00cd29b799e3 klist: fix starting 
point removed bug in klist iterators)
Merging tty.current/tty-linus (c8053b587627 Revert "8250: uniphier: allow 
modular build with 8250 console")
Merging usb.current/usb-linus (89140fdaf11a xhci: harden xhci_find_next_ext_cap 
against device removal)
Merging usb-gadget-fixes/fixes (6a4290cc28be usb: dwc3: gadget: set the OTG 
flag in dwc3 gadget driver.)
Merging usb-serial-fixes/usb-linus (4152b387da81 USB: option: fix Cinterion 
AHxx enumeration)
Merging usb-chipidea-fixes/ci-for-usb-stable (6f51bc340d2a usb: chipidea: imx: 
fix a possible NULL dereference)
Merging staging.current/staging-linus (388f7b1d6e8c Linux 4.5-rc3)
Merging char-misc.current/char-misc-linus (3b2b9ead3214 nvmem: qfprom: Specify 
LE device endianness)
Merging input-current/for-linus (ff84dabe3c6e Input: colibri-vf50-ts - add 
missing #include )
Merging crypto-current/master (8a3978ad55fb crypto: marvell/cesa - fix test in 
mv_cesa_dev_dma_init())
Merging ide/master (e04a2bd6d8c9 drivers/ide: make ide-scan-pci.c driver 
explicitly non-modular)
Merging devicetree-current/devicetree/merge (f76502aa9140 of/dynamic: Fix test 
for PPC_PSERIES)
Merging rr-fixes/fixes (8244062ef1e5 modules: fix longstanding /proc/kallsyms 
vs module insertion race.)
Merging vfio-fixes/for-linus (16ab8a5cbea4 vfio/noiommu: Don't use 
iommu_present() to track fake groups)

Re: linux-next: Tree for Feb 12

2016-02-11 Thread Sudip Mukherjee
On Fri, Feb 12, 2016 at 04:20:35PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20160211:

since last few days with gcc-4.6.3, x86_64 and i386 defconfig and
allmodconfig builds are failing with the error:
"arch/x86/include/asm/tlbflush.h:26:18: error: memory input 0 is not
directly addressable"

But with gcc-4.8.2 and later it builds fine. Should I try to bisect and
find the problem or its not worth for gcc-4.6.3 ?

regards
sudip



linux-next: Tree for Feb 12

2015-02-11 Thread Stephen Rothwell
Hi all,

Please do not add any material destined for v3.21 to your linux-next
included trees until after v3.20-rc1 has been released.

Changes since 20150211:

The net-next tree gained a conflict against Linus' tree.

The akpm-current tree gained a conflict against the modules tree.

Non-merge commits (relative to Linus' tree): 4912
 4799 files changed, 206475 insertions(+), 107119 deletions(-)



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log files
in the Next directory.  Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64 and a
multi_v7_defconfig for arm. After the final fixups (if any), it is also
built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and
allyesconfig (this fails its final link) and i386, sparc, sparc64 and arm
defconfig.

Below is a summary of the state of the merge.

I am currently merging 206 trees (counting Linus' and 30 trees of patches
pending for Linus' tree).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au

$ git checkout master
$ git reset --hard stable
Merging origin/master (73b4f63aebd6 Merge tag 'docs-for-linus' of 
git://git.lwn.net/linux-2.6)
Merging fixes/master (b94d525e58dc Merge 
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net)
Merging kbuild-current/rc-fixes (a16c5f99a28c kbuild: Fix removal of the 
debian/ directory)
Merging arc-current/for-curr (2ce7598c9a45 Linux 3.17-rc4)
Merging arm-current/fixes (8e6480667246 ARM: 8299/1: mm: ensure local active 
ASID is marked as allocated on rollover)
Merging m68k-current/for-linus (4436820a98cd m68k/defconfig: Enable Ethernet 
bridging)
Merging metag-fixes/fixes (ffe6902b66aa asm-generic: remove _STK_LIM_MAX)
Merging mips-fixes/mips-fixes (1795cd9b3a91 Linux 3.16-rc5)
Merging powerpc-merge/merge (31345e1a071e powerpc/pci: Remove unused 
force_32bit_msi quirk)
Merging powerpc-merge-mpe/fixes (c59c961ca511 Merge branch 'drm-fixes' of 
git://people.freedesktop.org/~airlied/linux)
Merging sparc/master (66d0f7ec9f10 sparc32: destroy_context() and switch_mm() 
needs to disable interrupts.)
Merging net/master (73b4f63aebd6 Merge tag 'docs-for-linus' of 
git://git.lwn.net/linux-2.6)
Merging ipsec/master (044a832a7779 xfrm: Fix local error reporting crash with 
interfamily tunnels)
Merging sound-current/for-linus (d2255c016365 Merge tag 
'asoc-fix-ac97-v3.19-rc7' of 
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus)
Merging pci-current/for-linus (06cf35f903aa PCI: Handle read-only BARs on AMD 
CS553x devices)
Merging wireless-drivers/master (aeb2d2a4c0ae rtlwifi: Remove logging statement 
that is no longer needed)
Merging driver-core.current/driver-core-linus (26bc420b59a3 Linux 3.19-rc6)
Merging tty.current/tty-linus (ec6f34e5b552 Linux 3.19-rc5)
Merging usb.current/usb-linus (e36f014edff7 Linux 3.19-rc7)
Merging usb-gadget-fixes/fixes (0df8fc37f6e4 usb: phy: never defer probe in 
non-OF case)
Merging usb-serial-fixes/usb-linus (a6f0331236fa USB: cp210x: add ID for 
RUGGEDCOM USB Serial Console)
Merging staging.current/staging-linus (e36f014edff7 Linux 3.19-rc7)
Merging char-misc.current/char-misc-linus (e36f014edff7 Linux 3.19-rc7)
Merging input-current/for-linus (4ba24fef3eb3 Merge branch 'next' into 
for-linus)
Merging crypto-current/master (3e14dcf7cb80 crypto: add missing crypto module 
aliases)
Merging ide/master (f96fe225677b Merge 
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net)
Merging devicetree-current/devicetree/merge (6b1271de3723 of/unittest: Overlays 
with sub-devices tests)
Merging rr-fixes/fixes (dc4515ea26d6 scsi: always increment reference count)
Merging vfio-fixes/for-linus (7c2e211f3c95 vfio-pci: Fix the check on pci 
device type in vfio_pci_probe())
Merging kselftest-fixes/fixes (f5db310d77ef selftests/vm: fix link error for 
transhuge-stress test)
Merging drm-intel-fixes/for-linux-next-fixes (bfa76d495765 Linux 3.19)
Merging asm-generic/master (643165c8bbc8 Merge tag 'uaccess_for_upstream' of 

linux-next: Tree for Feb 12

2015-02-11 Thread Stephen Rothwell
Hi all,

Please do not add any material destined for v3.21 to your linux-next
included trees until after v3.20-rc1 has been released.

Changes since 20150211:

The net-next tree gained a conflict against Linus' tree.

The akpm-current tree gained a conflict against the modules tree.

Non-merge commits (relative to Linus' tree): 4912
 4799 files changed, 206475 insertions(+), 107119 deletions(-)



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use git pull
to do so as that will try to merge the new linux-next release with the
old one.  You should use git fetch and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log files
in the Next directory.  Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64 and a
multi_v7_defconfig for arm. After the final fixups (if any), it is also
built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and
allyesconfig (this fails its final link) and i386, sparc, sparc64 and arm
defconfig.

Below is a summary of the state of the merge.

I am currently merging 206 trees (counting Linus' and 30 trees of patches
pending for Linus' tree).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au

$ git checkout master
$ git reset --hard stable
Merging origin/master (73b4f63aebd6 Merge tag 'docs-for-linus' of 
git://git.lwn.net/linux-2.6)
Merging fixes/master (b94d525e58dc Merge 
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net)
Merging kbuild-current/rc-fixes (a16c5f99a28c kbuild: Fix removal of the 
debian/ directory)
Merging arc-current/for-curr (2ce7598c9a45 Linux 3.17-rc4)
Merging arm-current/fixes (8e6480667246 ARM: 8299/1: mm: ensure local active 
ASID is marked as allocated on rollover)
Merging m68k-current/for-linus (4436820a98cd m68k/defconfig: Enable Ethernet 
bridging)
Merging metag-fixes/fixes (ffe6902b66aa asm-generic: remove _STK_LIM_MAX)
Merging mips-fixes/mips-fixes (1795cd9b3a91 Linux 3.16-rc5)
Merging powerpc-merge/merge (31345e1a071e powerpc/pci: Remove unused 
force_32bit_msi quirk)
Merging powerpc-merge-mpe/fixes (c59c961ca511 Merge branch 'drm-fixes' of 
git://people.freedesktop.org/~airlied/linux)
Merging sparc/master (66d0f7ec9f10 sparc32: destroy_context() and switch_mm() 
needs to disable interrupts.)
Merging net/master (73b4f63aebd6 Merge tag 'docs-for-linus' of 
git://git.lwn.net/linux-2.6)
Merging ipsec/master (044a832a7779 xfrm: Fix local error reporting crash with 
interfamily tunnels)
Merging sound-current/for-linus (d2255c016365 Merge tag 
'asoc-fix-ac97-v3.19-rc7' of 
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus)
Merging pci-current/for-linus (06cf35f903aa PCI: Handle read-only BARs on AMD 
CS553x devices)
Merging wireless-drivers/master (aeb2d2a4c0ae rtlwifi: Remove logging statement 
that is no longer needed)
Merging driver-core.current/driver-core-linus (26bc420b59a3 Linux 3.19-rc6)
Merging tty.current/tty-linus (ec6f34e5b552 Linux 3.19-rc5)
Merging usb.current/usb-linus (e36f014edff7 Linux 3.19-rc7)
Merging usb-gadget-fixes/fixes (0df8fc37f6e4 usb: phy: never defer probe in 
non-OF case)
Merging usb-serial-fixes/usb-linus (a6f0331236fa USB: cp210x: add ID for 
RUGGEDCOM USB Serial Console)
Merging staging.current/staging-linus (e36f014edff7 Linux 3.19-rc7)
Merging char-misc.current/char-misc-linus (e36f014edff7 Linux 3.19-rc7)
Merging input-current/for-linus (4ba24fef3eb3 Merge branch 'next' into 
for-linus)
Merging crypto-current/master (3e14dcf7cb80 crypto: add missing crypto module 
aliases)
Merging ide/master (f96fe225677b Merge 
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net)
Merging devicetree-current/devicetree/merge (6b1271de3723 of/unittest: Overlays 
with sub-devices tests)
Merging rr-fixes/fixes (dc4515ea26d6 scsi: always increment reference count)
Merging vfio-fixes/for-linus (7c2e211f3c95 vfio-pci: Fix the check on pci 
device type in vfio_pci_probe())
Merging kselftest-fixes/fixes (f5db310d77ef selftests/vm: fix link error for 
transhuge-stress test)
Merging drm-intel-fixes/for-linux-next-fixes (bfa76d495765 Linux 3.19)
Merging asm-generic/master (643165c8bbc8 Merge tag 'uaccess_for_upstream' of 

linux-next: Tree for Feb 12

2014-02-11 Thread Stephen Rothwell
Hi all,

If you see failures in building this tree due to missing declarations of
k..alloc/free, then it may be caused by commit 2bd59d48ebfb ("cgroup:
convert to kernfs").  Please send Tejun Heo  a patch
adding an inclusion of linux/slab.h to the appropriate file(s).

This tree fails (more than usual) the powerpc allyesconfig build.

Changes since 20140210:

The powerpc tree still had its build failure.

The mfd-lj tree still had its build failure so I used the version from
next-20140210.

The tip tree lost its build failure but gained another so I used the
version from next-20140210.

The staging tree lost its build failure.

The cgroup tree gained a build failure for which I applied a patch.

The pinctrl tree lost its build failure.

Non-merge commits (relative to Linus' tree): 1763
 1848 files changed, 64228 insertions(+), 31255 deletions(-)



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" as mentioned in the FAQ on the wiki
(see below).

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log files
in the Next directory.  Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64 and a
multi_v7_defconfig for arm. After the final fixups (if any), it is also
built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and
allyesconfig (minus CONFIG_PROFILE_ALL_BRANCHES - this fails its final
link) and i386, sparc, sparc64 and arm defconfig. These builds also have
CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and
CONFIG_DEBUG_INFO disabled when necessary.

Below is a summary of the state of the merge.

I am currently merging 208 trees (counting Linus' and 28 trees of patches
pending for Linus' tree).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

There is a wiki covering stuff to do with linux-next at
http://linux.f-seidel.de/linux-next/pmwiki/ .  Thanks to Frank Seidel.

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au

$ git checkout master
$ git reset --hard stable
Merging origin/master (738b52bb9845 Merge tag 'microblaze-3.14-rc3' of 
git://git.monstr.eu/linux-2.6-microblaze)
Merging fixes/master (b0031f227e47 Merge tag 's2mps11-build' of 
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator)
Merging kbuild-current/rc-fixes (38dbfb59d117 Linus 3.14-rc1)
Merging arc-current/for-curr (7e22e91102c6 Linux 3.13-rc8)
Merging arm-current/fixes (87f9260bf1fb ARM: dts: fix spdif pinmux 
configuration)
Merging m68k-current/for-linus (7247f55381d5 m68k: Wire up sched_setattr and 
sched_getattr)
Merging metag-fixes/fixes (3b2f64d00c46 Linux 3.11-rc2)
Merging powerpc-merge/merge (b3084f4db3ae powerpc/thp: Fix crash on mremap)
Merging sparc/master (738b52bb9845 Merge tag 'microblaze-3.14-rc3' of 
git://git.monstr.eu/linux-2.6-microblaze)
Merging net/master (738b52bb9845 Merge tag 'microblaze-3.14-rc3' of 
git://git.monstr.eu/linux-2.6-microblaze)
Merging ipsec/master (965cdea82569 dccp: catch failed request_module call in 
dccp_probe init)
Merging sound-current/for-linus (ef8e39b51f24 ALSA: hda - Fix undefined symbol 
due to builtin/module mixup)
Merging pci-current/for-linus (38dbfb59d117 Linus 3.14-rc1)
Merging wireless/master (348f7d4adee9 rtl8180: Add error check for 
pci_map_single return value in TX path)
Merging driver-core.current/driver-core-linus (9e1ccb4a7700 drivers/base: fix 
devres handling for master device)
Merging tty.current/tty-linus (d8a5dc3033af tty: Set correct tty name in 
'active' sysfs attribute)
Merging usb.current/usb-linus (3635c7e2d59f usb: option: blacklist ZTE MF667 
net interface)
Merging staging.current/staging-linus (a0f452520211 Merge tag 
'iio-fixes-for-3.14b' of 
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-linus)
Merging char-misc.current/char-misc-linus (3b1cc9b9622a misc: mic: fix possible 
signed underflow (undefined behavior) in userspace API)
Merging input-current/for-linus (55df811f2066 Merge branch 'next' into 
for-linus)
Merging md-current/for-linus (d47648fcf061 raid5: avoid finding "discard" 
stripe)
Merging crypto-current/master (ee97dc7db4cb crypto: s390 - fix des and des3_ede 
ctr concurrency issue)
Merging ide/master (738b52bb9845 

linux-next: Tree for Feb 12

2014-02-11 Thread Stephen Rothwell
Hi all,

If you see failures in building this tree due to missing declarations of
k..alloc/free, then it may be caused by commit 2bd59d48ebfb (cgroup:
convert to kernfs).  Please send Tejun Heo t...@kernel.org a patch
adding an inclusion of linux/slab.h to the appropriate file(s).

This tree fails (more than usual) the powerpc allyesconfig build.

Changes since 20140210:

The powerpc tree still had its build failure.

The mfd-lj tree still had its build failure so I used the version from
next-20140210.

The tip tree lost its build failure but gained another so I used the
version from next-20140210.

The staging tree lost its build failure.

The cgroup tree gained a build failure for which I applied a patch.

The pinctrl tree lost its build failure.

Non-merge commits (relative to Linus' tree): 1763
 1848 files changed, 64228 insertions(+), 31255 deletions(-)



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use git pull
to do so as that will try to merge the new linux-next release with the
old one.  You should use git fetch as mentioned in the FAQ on the wiki
(see below).

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log files
in the Next directory.  Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64 and a
multi_v7_defconfig for arm. After the final fixups (if any), it is also
built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and
allyesconfig (minus CONFIG_PROFILE_ALL_BRANCHES - this fails its final
link) and i386, sparc, sparc64 and arm defconfig. These builds also have
CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and
CONFIG_DEBUG_INFO disabled when necessary.

Below is a summary of the state of the merge.

I am currently merging 208 trees (counting Linus' and 28 trees of patches
pending for Linus' tree).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

There is a wiki covering stuff to do with linux-next at
http://linux.f-seidel.de/linux-next/pmwiki/ .  Thanks to Frank Seidel.

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au

$ git checkout master
$ git reset --hard stable
Merging origin/master (738b52bb9845 Merge tag 'microblaze-3.14-rc3' of 
git://git.monstr.eu/linux-2.6-microblaze)
Merging fixes/master (b0031f227e47 Merge tag 's2mps11-build' of 
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator)
Merging kbuild-current/rc-fixes (38dbfb59d117 Linus 3.14-rc1)
Merging arc-current/for-curr (7e22e91102c6 Linux 3.13-rc8)
Merging arm-current/fixes (87f9260bf1fb ARM: dts: fix spdif pinmux 
configuration)
Merging m68k-current/for-linus (7247f55381d5 m68k: Wire up sched_setattr and 
sched_getattr)
Merging metag-fixes/fixes (3b2f64d00c46 Linux 3.11-rc2)
Merging powerpc-merge/merge (b3084f4db3ae powerpc/thp: Fix crash on mremap)
Merging sparc/master (738b52bb9845 Merge tag 'microblaze-3.14-rc3' of 
git://git.monstr.eu/linux-2.6-microblaze)
Merging net/master (738b52bb9845 Merge tag 'microblaze-3.14-rc3' of 
git://git.monstr.eu/linux-2.6-microblaze)
Merging ipsec/master (965cdea82569 dccp: catch failed request_module call in 
dccp_probe init)
Merging sound-current/for-linus (ef8e39b51f24 ALSA: hda - Fix undefined symbol 
due to builtin/module mixup)
Merging pci-current/for-linus (38dbfb59d117 Linus 3.14-rc1)
Merging wireless/master (348f7d4adee9 rtl8180: Add error check for 
pci_map_single return value in TX path)
Merging driver-core.current/driver-core-linus (9e1ccb4a7700 drivers/base: fix 
devres handling for master device)
Merging tty.current/tty-linus (d8a5dc3033af tty: Set correct tty name in 
'active' sysfs attribute)
Merging usb.current/usb-linus (3635c7e2d59f usb: option: blacklist ZTE MF667 
net interface)
Merging staging.current/staging-linus (a0f452520211 Merge tag 
'iio-fixes-for-3.14b' of 
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-linus)
Merging char-misc.current/char-misc-linus (3b1cc9b9622a misc: mic: fix possible 
signed underflow (undefined behavior) in userspace API)
Merging input-current/for-linus (55df811f2066 Merge branch 'next' into 
for-linus)
Merging md-current/for-linus (d47648fcf061 raid5: avoid finding discard 
stripe)
Merging crypto-current/master (ee97dc7db4cb crypto: s390 - fix des and des3_ede 
ctr concurrency issue)
Merging ide/master 

Re: linux-next: Tree for Feb 12 (drm_pci.c)

2013-02-12 Thread Bjorn Helgaas
On Tue, Feb 12, 2013 at 08:06:00AM -0800, Randy Dunlap wrote:
> On 02/11/13 21:09, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20130211:
> > 
> 
> 
> when CONFIG_PCI is not enabled (on x86_64):
> 
>   CC [M]  drivers/gpu/drm/drm_pci.o
> drivers/gpu/drm/drm_pci.c: In function 'drm_pcie_get_speed_cap_mask':
> drivers/gpu/drm/drm_pci.c:485:2: error: implicit declaration of function 
> 'pcie_capability_read_dword' [-Werror=implicit-function-declaration]
> cc1: some warnings being treated as errors
> make[4]: *** [drivers/gpu/drm/drm_pci.o] Error 1

This one is my fault.  I sent the following patch to Dave to fix it up.


commit ed0708e69f71fab656afc1c891f3c54c9b105664
Author: Bjorn Helgaas 
Date:   Fri Feb 8 15:18:35 2013 -0700

drm/pci: define drm_pcie_get_speed_cap_mask() only when CONFIG_PCI=y

Move drm_pcie_get_speed_cap_mask() under #ifdef CONFIG_PCI because it
it used only for PCI devices (evergreen, r600, r770), and it uses
PCI interfaces that only exist when CONFIG_PCI=y.

Previously, we tried to compile drm_pcie_get_speed_cap_mask() even when
CONFIG_PCI=n, which fails.

Tested-by: Fengguang Wu 
Signed-off-by: Bjorn Helgaas 

diff --git a/drivers/gpu/drm/drm_pci.c b/drivers/gpu/drm/drm_pci.c
index 754bc96..2b818c7 100644
--- a/drivers/gpu/drm/drm_pci.c
+++ b/drivers/gpu/drm/drm_pci.c
@@ -439,33 +439,6 @@ int drm_pci_init(struct drm_driver *driver, struct 
pci_driver *pdriver)
return 0;
 }
 
-#else
-
-int drm_pci_init(struct drm_driver *driver, struct pci_driver *pdriver)
-{
-   return -1;
-}
-
-#endif
-
-EXPORT_SYMBOL(drm_pci_init);
-
-/*@}*/
-void drm_pci_exit(struct drm_driver *driver, struct pci_driver *pdriver)
-{
-   struct drm_device *dev, *tmp;
-   DRM_DEBUG("\n");
-
-   if (driver->driver_features & DRIVER_MODESET) {
-   pci_unregister_driver(pdriver);
-   } else {
-   list_for_each_entry_safe(dev, tmp, >device_list, 
driver_item)
-   drm_put_dev(dev);
-   }
-   DRM_INFO("Module unloaded\n");
-}
-EXPORT_SYMBOL(drm_pci_exit);
-
 int drm_pcie_get_speed_cap_mask(struct drm_device *dev, u32 *mask)
 {
struct pci_dev *root;
@@ -514,3 +487,30 @@ int drm_pcie_get_speed_cap_mask(struct drm_device *dev, 
u32 *mask)
return 0;
 }
 EXPORT_SYMBOL(drm_pcie_get_speed_cap_mask);
+
+#else
+
+int drm_pci_init(struct drm_driver *driver, struct pci_driver *pdriver)
+{
+   return -1;
+}
+
+#endif
+
+EXPORT_SYMBOL(drm_pci_init);
+
+/*@}*/
+void drm_pci_exit(struct drm_driver *driver, struct pci_driver *pdriver)
+{
+   struct drm_device *dev, *tmp;
+   DRM_DEBUG("\n");
+
+   if (driver->driver_features & DRIVER_MODESET) {
+   pci_unregister_driver(pdriver);
+   } else {
+   list_for_each_entry_safe(dev, tmp, >device_list, 
driver_item)
+   drm_put_dev(dev);
+   }
+   DRM_INFO("Module unloaded\n");
+}
+EXPORT_SYMBOL(drm_pci_exit);
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: linux-next: Tree for Feb 12 [ WARNING: at drivers/tty/tty_buffer.c:427 flush_to_ldisc | tty is NULL ]

2013-02-12 Thread Sedat Dilek
On Tue, Feb 12, 2013 at 6:09 AM, Stephen Rothwell  wrote:
> Hi all,
>
> Changes since 20130211:
>
> The acpi tree lost its build failure.
>
> The net-next tree gained a conflict against the net tree.
>
> The arm-soc tree gained conflicts against the usb and metag trees.
>
> 
>

[ CCing linux-serial and linux-pm folks ]

When starting suspend (seen once, 2nd suspend was OK)...

[  706.950122] PM: Syncing filesystems ... done.
[  706.953773] PM: Preparing system for mem sleep
[  726.174449] [ cut here ]
[  726.174469] WARNING: at drivers/tty/tty_buffer.c:427
flush_to_ldisc+0x1ac/0x1c0()
[  726.174473] Hardware name: 530U3BI/530U4BI/530U4BH
[  726.174476] tty is NULL
[  707.034695] Freezing user space processes ...
[  726.174479] Modules linked in: btrfs zlib_deflate xfs libcrc32c
bnep rfcomm parport_pc ppdev snd_hda_codec_hdmi snd_hda_codec_realtek
coretemp kvm_intel arc4 kvm iwldvm mac80211 snd_hda_intel
ghash_clmulni_intel aesni_intel snd_hda_codec xts uvcvideo aes_x86_64
snd_hwdep snd_pcm lrw gf128mul videobuf2_vmalloc ablk_helper
snd_page_alloc joydev videobuf2_memops i915 cryptd snd_seq_midi
videobuf2_core snd_seq_midi_event videodev iwlwifi snd_rawmidi snd_seq
snd_timer snd_seq_device i2c_algo_bit drm_kms_helper cfg80211 btusb
snd psmouse drm soundcore microcode bluetooth samsung_laptop serio_raw
wmi lpc_ich mei mac_hid video lp parport hid_generic usbhid hid r8169
[  726.174529] Pid: 2507, comm: kworker/0:0 Not tainted
3.8.0-rc7-next20130212-3-iniza-small #1
[  726.174530] Call Trace:
[  726.174535]  [] warn_slowpath_common+0x7f/0xc0
[  726.174538]  [] warn_slowpath_fmt+0x46/0x50
[  726.174541]  [] flush_to_ldisc+0x1ac/0x1c0
[  726.174544]  [] process_one_work+0x16b/0x400
[  726.174547]  [] worker_thread+0x118/0x360
[  726.174549]  [] ? manage_workers+0x350/0x350
[  726.174552]  [] kthread+0xc0/0xd0
[  726.174554]  [] ? flush_kthread_worker+0xb0/0xb0
[  726.174557]  [] ret_from_fork+0x7c/0xb0
[  726.174559]  [] ? flush_kthread_worker+0xb0/0xb0
[  726.174560] ---[ end trace bf493695d326ce7b ]---
[  726.379024] [ cut here ]

 - Sedat -
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: linux-next: Tree for Feb 12 (drm_pci.c)

2013-02-12 Thread Randy Dunlap
On 02/11/13 21:09, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20130211:
> 


when CONFIG_PCI is not enabled (on x86_64):

  CC [M]  drivers/gpu/drm/drm_pci.o
drivers/gpu/drm/drm_pci.c: In function 'drm_pcie_get_speed_cap_mask':
drivers/gpu/drm/drm_pci.c:485:2: error: implicit declaration of function 
'pcie_capability_read_dword' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[4]: *** [drivers/gpu/drm/drm_pci.o] Error 1



-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: linux-next: Tree for Feb 12 (drm_pci.c)

2013-02-12 Thread Randy Dunlap
On 02/11/13 21:09, Stephen Rothwell wrote:
 Hi all,
 
 Changes since 20130211:
 


when CONFIG_PCI is not enabled (on x86_64):

  CC [M]  drivers/gpu/drm/drm_pci.o
drivers/gpu/drm/drm_pci.c: In function 'drm_pcie_get_speed_cap_mask':
drivers/gpu/drm/drm_pci.c:485:2: error: implicit declaration of function 
'pcie_capability_read_dword' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[4]: *** [drivers/gpu/drm/drm_pci.o] Error 1



-- 
~Randy
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: linux-next: Tree for Feb 12 [ WARNING: at drivers/tty/tty_buffer.c:427 flush_to_ldisc | tty is NULL ]

2013-02-12 Thread Sedat Dilek
On Tue, Feb 12, 2013 at 6:09 AM, Stephen Rothwell s...@canb.auug.org.au wrote:
 Hi all,

 Changes since 20130211:

 The acpi tree lost its build failure.

 The net-next tree gained a conflict against the net tree.

 The arm-soc tree gained conflicts against the usb and metag trees.

 


[ CCing linux-serial and linux-pm folks ]

When starting suspend (seen once, 2nd suspend was OK)...

[  706.950122] PM: Syncing filesystems ... done.
[  706.953773] PM: Preparing system for mem sleep
[  726.174449] [ cut here ]
[  726.174469] WARNING: at drivers/tty/tty_buffer.c:427
flush_to_ldisc+0x1ac/0x1c0()
[  726.174473] Hardware name: 530U3BI/530U4BI/530U4BH
[  726.174476] tty is NULL
[  707.034695] Freezing user space processes ...
[  726.174479] Modules linked in: btrfs zlib_deflate xfs libcrc32c
bnep rfcomm parport_pc ppdev snd_hda_codec_hdmi snd_hda_codec_realtek
coretemp kvm_intel arc4 kvm iwldvm mac80211 snd_hda_intel
ghash_clmulni_intel aesni_intel snd_hda_codec xts uvcvideo aes_x86_64
snd_hwdep snd_pcm lrw gf128mul videobuf2_vmalloc ablk_helper
snd_page_alloc joydev videobuf2_memops i915 cryptd snd_seq_midi
videobuf2_core snd_seq_midi_event videodev iwlwifi snd_rawmidi snd_seq
snd_timer snd_seq_device i2c_algo_bit drm_kms_helper cfg80211 btusb
snd psmouse drm soundcore microcode bluetooth samsung_laptop serio_raw
wmi lpc_ich mei mac_hid video lp parport hid_generic usbhid hid r8169
[  726.174529] Pid: 2507, comm: kworker/0:0 Not tainted
3.8.0-rc7-next20130212-3-iniza-small #1
[  726.174530] Call Trace:
[  726.174535]  [8105a5ef] warn_slowpath_common+0x7f/0xc0
[  726.174538]  [8105a6e6] warn_slowpath_fmt+0x46/0x50
[  726.174541]  [8142415c] flush_to_ldisc+0x1ac/0x1c0
[  726.174544]  [8107993b] process_one_work+0x16b/0x400
[  726.174547]  [8107a5b8] worker_thread+0x118/0x360
[  726.174549]  [8107a4a0] ? manage_workers+0x350/0x350
[  726.174552]  [8107fab0] kthread+0xc0/0xd0
[  726.174554]  [8107f9f0] ? flush_kthread_worker+0xb0/0xb0
[  726.174557]  [816cabac] ret_from_fork+0x7c/0xb0
[  726.174559]  [8107f9f0] ? flush_kthread_worker+0xb0/0xb0
[  726.174560] ---[ end trace bf493695d326ce7b ]---
[  726.379024] [ cut here ]

 - Sedat -
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: linux-next: Tree for Feb 12 (drm_pci.c)

2013-02-12 Thread Bjorn Helgaas
On Tue, Feb 12, 2013 at 08:06:00AM -0800, Randy Dunlap wrote:
 On 02/11/13 21:09, Stephen Rothwell wrote:
  Hi all,
  
  Changes since 20130211:
  
 
 
 when CONFIG_PCI is not enabled (on x86_64):
 
   CC [M]  drivers/gpu/drm/drm_pci.o
 drivers/gpu/drm/drm_pci.c: In function 'drm_pcie_get_speed_cap_mask':
 drivers/gpu/drm/drm_pci.c:485:2: error: implicit declaration of function 
 'pcie_capability_read_dword' [-Werror=implicit-function-declaration]
 cc1: some warnings being treated as errors
 make[4]: *** [drivers/gpu/drm/drm_pci.o] Error 1

This one is my fault.  I sent the following patch to Dave to fix it up.


commit ed0708e69f71fab656afc1c891f3c54c9b105664
Author: Bjorn Helgaas bhelg...@google.com
Date:   Fri Feb 8 15:18:35 2013 -0700

drm/pci: define drm_pcie_get_speed_cap_mask() only when CONFIG_PCI=y

Move drm_pcie_get_speed_cap_mask() under #ifdef CONFIG_PCI because it
it used only for PCI devices (evergreen, r600, r770), and it uses
PCI interfaces that only exist when CONFIG_PCI=y.

Previously, we tried to compile drm_pcie_get_speed_cap_mask() even when
CONFIG_PCI=n, which fails.

Tested-by: Fengguang Wu fengguang...@intel.com
Signed-off-by: Bjorn Helgaas bhelg...@google.com

diff --git a/drivers/gpu/drm/drm_pci.c b/drivers/gpu/drm/drm_pci.c
index 754bc96..2b818c7 100644
--- a/drivers/gpu/drm/drm_pci.c
+++ b/drivers/gpu/drm/drm_pci.c
@@ -439,33 +439,6 @@ int drm_pci_init(struct drm_driver *driver, struct 
pci_driver *pdriver)
return 0;
 }
 
-#else
-
-int drm_pci_init(struct drm_driver *driver, struct pci_driver *pdriver)
-{
-   return -1;
-}
-
-#endif
-
-EXPORT_SYMBOL(drm_pci_init);
-
-/*@}*/
-void drm_pci_exit(struct drm_driver *driver, struct pci_driver *pdriver)
-{
-   struct drm_device *dev, *tmp;
-   DRM_DEBUG(\n);
-
-   if (driver-driver_features  DRIVER_MODESET) {
-   pci_unregister_driver(pdriver);
-   } else {
-   list_for_each_entry_safe(dev, tmp, driver-device_list, 
driver_item)
-   drm_put_dev(dev);
-   }
-   DRM_INFO(Module unloaded\n);
-}
-EXPORT_SYMBOL(drm_pci_exit);
-
 int drm_pcie_get_speed_cap_mask(struct drm_device *dev, u32 *mask)
 {
struct pci_dev *root;
@@ -514,3 +487,30 @@ int drm_pcie_get_speed_cap_mask(struct drm_device *dev, 
u32 *mask)
return 0;
 }
 EXPORT_SYMBOL(drm_pcie_get_speed_cap_mask);
+
+#else
+
+int drm_pci_init(struct drm_driver *driver, struct pci_driver *pdriver)
+{
+   return -1;
+}
+
+#endif
+
+EXPORT_SYMBOL(drm_pci_init);
+
+/*@}*/
+void drm_pci_exit(struct drm_driver *driver, struct pci_driver *pdriver)
+{
+   struct drm_device *dev, *tmp;
+   DRM_DEBUG(\n);
+
+   if (driver-driver_features  DRIVER_MODESET) {
+   pci_unregister_driver(pdriver);
+   } else {
+   list_for_each_entry_safe(dev, tmp, driver-device_list, 
driver_item)
+   drm_put_dev(dev);
+   }
+   DRM_INFO(Module unloaded\n);
+}
+EXPORT_SYMBOL(drm_pci_exit);
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/