linux-next: Tree for Jan 19

[Stephen Rothwell]

Hi all,

Changes since 20210118:

The hid tree gained a conflict against the qcom tree.

The drm tree still had its build failure so I used the version from
next-20210107.

The drm-intel tree still had its build failure from merging the drm tree,
so I have used the version from next-20210108.

I still reverted a commit from the iomem-mmap-vs-gup tree that caused
a boot failure on PowerPC.

The oprofile-removal tree lost its build failure.

Non-merge commits (relative to Linus' tree): 3859
 4166 files changed, 153036 insertions(+), 80251 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 86 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 (1e2a199f6ccd Merge tag 'spi-fix-v5.11-rc4' of 
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi)
Merging fixes/fixes (e71ba9452f0b Linux 5.11-rc2)
Merging kbuild-current/fixes (0bc9bc1d8b2f Merge tag 'ext4_for_linus_stable' of 
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4)
Merging arc-current/for-curr (7c53f6b671f4 Linux 5.11-rc3)
Merging arm-current/fixes (e64ab473ddda ARM: 9034/1: __div64_32(): straighten 
up inline asm constraints)
Merging arm64-fixes/for-next/fixes (3ed86b9a7140 kasan, arm64: fix pointer tags 
in KASAN reports)
Merging arm-soc-fixes/arm/fixes (8a996b2d8a03 ARM: dts: ux500: Reserve memory 
carveouts)
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 (41131a5e54ae powerpc/vdso: Fix 
clock_gettime_fallback for vdso32)
Merging s390-fixes/fixes (a1a322a62dba s390/vfio-ap: clean up vfio_ap resources 
when KVM pointer invalidated)
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 (87fe04367d84 net: dsa: mv88e6xxx: also read STU state in 
mv88e6250_g1_vtu_getnext)
Merging bpf/master (e23a8d002198 Merge 
https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf)
Merging ipsec/master (da64ae2d35d3 xfrm: Fix wraparound in 
xfrm_policy_addr_delta())
Merging netfilter/master (c8a8ead01736 Merge 
git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf)
Merging ipvs/master (869f4fdaf4ca netfilter: nf_nat: Fix memleak in nf_nat_init)
Merging wireless-drivers/master (952de419b617 mt76: mt7663s: fix rx buffer 
refcounting)
Merging mac80211/master (c13cf5c15966 mac80211: check if atf has been disabled 
in __ieee80211_schedule_txq)
Merging rdma-fixes/for-rc (19c329f68089 Linux 5.11-rc4)
Merging sound-current/for-linus (c23010ffb20a Merge tag 'asoc-fix-v5.11-rc4' of 
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus)
Merging sound-asoc-fixes/for-linus (63e1267254ab Merge remote-tracking branch 
'asoc/for-5.11' into asoc-linus)
Merging regmap-fixes/for-linus (7c53f6b671f4 Linux 5.11-rc3)
Merging regulator-fixes/for-linus (09db7311ca61 Merge v5.11-rc3)
Merging spi-fixes/for-linus (4d163ad79b15 spi: cadence: cache reference clock 
rate during probe)
Merging pci-current/for-linus (7c53f6b671f4 Linux 5.11-rc3)
Merging driver-core.current/driver-core-linus (895bee270863 Revert "driver 
core: Reorder devices on successful 

linux-next: Tree for Jan 19

[Stephen Rothwell]

Hi all,

News: there will probably be very few, if any, releases next week as LCA
is on (unfortunate clash with the merge window).

Changes since 20180118:

The powerpc tree gained a build failure due to an interaction with Linus'
tree, so I applied a merge fix patch.  It gained another for which I
applied a supplied fix patch.

The f2fs tree gained a build failure due to an interaction with the
btrfs tree for which I reverted a commit.

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

Non-merge commits (relative to Linus' tree): 9833
 9793 files changed, 406830 insertions(+), 263432 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 (dda3e15231b3 Merge branch 'fixes' of 
git://git.armlinux.org.uk/~rmk/linux-arm)
Merging fixes/master (820bf5c419e4 Merge tag 'scsi-fixes' of 
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi)
Merging kbuild-current/fixes (36c1681678b5 genksyms: drop *.hash.c from 
.gitignore)
Merging arc-current/for-curr (8ff3afc159f2 ARC: Enable fatal signals on boot 
for dev platforms)
Merging arm-current/fixes (091f02483df7 ARM: net: bpf: clarify tail_call index)
Merging m68k-current/for-linus (5e387199c17c m68k/defconfig: Update defconfigs 
for v4.14-rc7)
Merging metag-fixes/fixes (b884a190afce metag/usercopy: Add missing fixups)
Merging powerpc-fixes/fixes (1b689a95ce74 powerpc/pseries: include 
linux/types.h in asm/hvcall.h)
Merging sparc/master (59585b4be9ae sparc64: repair calling incorrect hweight 
function from stubs)
Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2)
Merging net/master (b200bfd6112a fm10k: mark PM functions as __maybe_unused)
Merging bpf/master (7155f8f39157 Merge 
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf)
Merging ipsec/master (ad9294dbc227 bpf: fix cls_bpf on filter replace)
Merging netfilter/master (889c604fd0b5 netfilter: x_tables: fix int overflow in 
xt_alloc_table_info())
Merging ipvs/master (f7fb77fc1235 netfilter: nft_compat: check extension hook 
mask only if set)
Merging wireless-drivers/master (cc124d5cc8d8 brcmfmac: fix CLM load error for 
legacy chips when user helper is enabled)
Merging mac80211/master (59b179b48ce2 cfg80211: check dev_set_name() return 
value)
Merging rdma-fixes/for-rc (ae59c3f0b6cf RDMA/mlx5: Fix out-of-bound access 
while querying AH)
Merging sound-current/for-linus (b3defb791b26 ALSA: seq: Make ioctls race-free)
Merging pci-current/for-linus (d6c1efecd1e1 x86/PCI: Enable AMD 64-bit window 
on resume)
Merging driver-core.current/driver-core-linus (30a7acd57389 Linux 4.15-rc6)
Merging tty.current/tty-linus (30a7acd57389 Linux 4.15-rc6)
Merging usb.current/usb-linus (a8750ddca918 Linux 4.15-rc8)
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 (a8750ddca918 Linux 4.15-rc8)
Merging char-misc.current/char-misc-linus (a8750ddca918 Linux 4.15-rc8)
Merging input-current/for-linus (55edde9fff1a 

linux-next: Tree for Jan 19

[Stephen Rothwell]

Hi all,

News: there will probably be very few, if any, releases next week as LCA
is on (unfortunate clash with the merge window).

Changes since 20180118:

The powerpc tree gained a build failure due to an interaction with Linus'
tree, so I applied a merge fix patch.  It gained another for which I
applied a supplied fix patch.

The f2fs tree gained a build failure due to an interaction with the
btrfs tree for which I reverted a commit.

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

Non-merge commits (relative to Linus' tree): 9833
 9793 files changed, 406830 insertions(+), 263432 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 (dda3e15231b3 Merge branch 'fixes' of 
git://git.armlinux.org.uk/~rmk/linux-arm)
Merging fixes/master (820bf5c419e4 Merge tag 'scsi-fixes' of 
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi)
Merging kbuild-current/fixes (36c1681678b5 genksyms: drop *.hash.c from 
.gitignore)
Merging arc-current/for-curr (8ff3afc159f2 ARC: Enable fatal signals on boot 
for dev platforms)
Merging arm-current/fixes (091f02483df7 ARM: net: bpf: clarify tail_call index)
Merging m68k-current/for-linus (5e387199c17c m68k/defconfig: Update defconfigs 
for v4.14-rc7)
Merging metag-fixes/fixes (b884a190afce metag/usercopy: Add missing fixups)
Merging powerpc-fixes/fixes (1b689a95ce74 powerpc/pseries: include 
linux/types.h in asm/hvcall.h)
Merging sparc/master (59585b4be9ae sparc64: repair calling incorrect hweight 
function from stubs)
Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2)
Merging net/master (b200bfd6112a fm10k: mark PM functions as __maybe_unused)
Merging bpf/master (7155f8f39157 Merge 
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf)
Merging ipsec/master (ad9294dbc227 bpf: fix cls_bpf on filter replace)
Merging netfilter/master (889c604fd0b5 netfilter: x_tables: fix int overflow in 
xt_alloc_table_info())
Merging ipvs/master (f7fb77fc1235 netfilter: nft_compat: check extension hook 
mask only if set)
Merging wireless-drivers/master (cc124d5cc8d8 brcmfmac: fix CLM load error for 
legacy chips when user helper is enabled)
Merging mac80211/master (59b179b48ce2 cfg80211: check dev_set_name() return 
value)
Merging rdma-fixes/for-rc (ae59c3f0b6cf RDMA/mlx5: Fix out-of-bound access 
while querying AH)
Merging sound-current/for-linus (b3defb791b26 ALSA: seq: Make ioctls race-free)
Merging pci-current/for-linus (d6c1efecd1e1 x86/PCI: Enable AMD 64-bit window 
on resume)
Merging driver-core.current/driver-core-linus (30a7acd57389 Linux 4.15-rc6)
Merging tty.current/tty-linus (30a7acd57389 Linux 4.15-rc6)
Merging usb.current/usb-linus (a8750ddca918 Linux 4.15-rc8)
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 (a8750ddca918 Linux 4.15-rc8)
Merging char-misc.current/char-misc-linus (a8750ddca918 Linux 4.15-rc8)
Merging input-current/for-linus (55edde9fff1a 

Re: linux-next: Tree for Jan 19

[Paul Gortmaker]

[Re: linux-next: Tree for Jan 19] On 27/01/2017 (Fri 00:08) Stafford Horne 
wrote:

> On Thu, Jan 26, 2017 at 02:45:15PM +0900, Stafford Horne wrote:
> > On Wed, Jan 25, 2017 at 11:37:11AM -0500, Paul Gortmaker wrote:
> > > [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford 
> > > Horne wrote:
> > > 
> > > [...]
> > > 
> > > > 
> > > > Are all of these builds using the tests from lkp-tests [0]?
> > > 
> > > Not using any specific tests, other than compiling allmodconfig and
> > > defconfig.
> > > 
> > > > 
> > > > If so and no one is working on openrisc toolchain updates I will 
> > > > package up
> > > > a modern toolchain for the cdn [1] and send patches for lkp-test.
> > > > 
> > > > If there is something else that needs to be done let me know.
> > > > 
> > > > [0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> > > > [1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/
> > > 
> > > If you could work with Tony (his email is at the bottom of the crosstool
> > > front page in [1]) to get the or32 binutils updated, that would be
> > > great.  With all the arch currrently in linux, I pretty much have to
> > > just use what is available from kernel.org as prebuilts.
> > > 
> > 
> > Thanks,
> > 
> > I will followup with Tony.
> 
> Hi Paul,
> 
> Just in case you are interested I have uploaded toolchains to here:
> 
>   http://shorne.noip.me/crosstool/files/bin/x86_64/5.4.0/

Thanks, I was able to use this to build or32 defconfig.

Paul.
--

> 
> I will be sending the same (the files/patches dir) to Tony.

Re: linux-next: Tree for Jan 19

[Paul Gortmaker]

[Re: linux-next: Tree for Jan 19] On 27/01/2017 (Fri 00:08) Stafford Horne 
wrote:

> On Thu, Jan 26, 2017 at 02:45:15PM +0900, Stafford Horne wrote:
> > On Wed, Jan 25, 2017 at 11:37:11AM -0500, Paul Gortmaker wrote:
> > > [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford 
> > > Horne wrote:
> > > 
> > > [...]
> > > 
> > > > 
> > > > Are all of these builds using the tests from lkp-tests [0]?
> > > 
> > > Not using any specific tests, other than compiling allmodconfig and
> > > defconfig.
> > > 
> > > > 
> > > > If so and no one is working on openrisc toolchain updates I will 
> > > > package up
> > > > a modern toolchain for the cdn [1] and send patches for lkp-test.
> > > > 
> > > > If there is something else that needs to be done let me know.
> > > > 
> > > > [0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> > > > [1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/
> > > 
> > > If you could work with Tony (his email is at the bottom of the crosstool
> > > front page in [1]) to get the or32 binutils updated, that would be
> > > great.  With all the arch currrently in linux, I pretty much have to
> > > just use what is available from kernel.org as prebuilts.
> > > 
> > 
> > Thanks,
> > 
> > I will followup with Tony.
> 
> Hi Paul,
> 
> Just in case you are interested I have uploaded toolchains to here:
> 
>   http://shorne.noip.me/crosstool/files/bin/x86_64/5.4.0/

Thanks, I was able to use this to build or32 defconfig.

Paul.
--

> 
> I will be sending the same (the files/patches dir) to Tony.

Re: linux-next: Tree for Jan 19

[Stafford Horne]

On Thu, Jan 26, 2017 at 02:45:15PM +0900, Stafford Horne wrote:
> On Wed, Jan 25, 2017 at 11:37:11AM -0500, Paul Gortmaker wrote:
> > [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne 
> > wrote:
> > 
> > [...]
> > 
> > > 
> > > Are all of these builds using the tests from lkp-tests [0]?
> > 
> > Not using any specific tests, other than compiling allmodconfig and
> > defconfig.
> > 
> > > 
> > > If so and no one is working on openrisc toolchain updates I will package 
> > > up
> > > a modern toolchain for the cdn [1] and send patches for lkp-test.
> > > 
> > > If there is something else that needs to be done let me know.
> > > 
> > > [0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> > > [1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/
> > 
> > If you could work with Tony (his email is at the bottom of the crosstool
> > front page in [1]) to get the or32 binutils updated, that would be
> > great.  With all the arch currrently in linux, I pretty much have to
> > just use what is available from kernel.org as prebuilts.
> > 
> 
> Thanks,
> 
> I will followup with Tony.

Hi Paul,

Just in case you are interested I have uploaded toolchains to here:

  http://shorne.noip.me/crosstool/files/bin/x86_64/5.4.0/

I will be sending the same (the files/patches dir) to Tony.

Re: linux-next: Tree for Jan 19

[Stafford Horne]

On Thu, Jan 26, 2017 at 02:45:15PM +0900, Stafford Horne wrote:
> On Wed, Jan 25, 2017 at 11:37:11AM -0500, Paul Gortmaker wrote:
> > [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne 
> > wrote:
> > 
> > [...]
> > 
> > > 
> > > Are all of these builds using the tests from lkp-tests [0]?
> > 
> > Not using any specific tests, other than compiling allmodconfig and
> > defconfig.
> > 
> > > 
> > > If so and no one is working on openrisc toolchain updates I will package 
> > > up
> > > a modern toolchain for the cdn [1] and send patches for lkp-test.
> > > 
> > > If there is something else that needs to be done let me know.
> > > 
> > > [0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> > > [1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/
> > 
> > If you could work with Tony (his email is at the bottom of the crosstool
> > front page in [1]) to get the or32 binutils updated, that would be
> > great.  With all the arch currrently in linux, I pretty much have to
> > just use what is available from kernel.org as prebuilts.
> > 
> 
> Thanks,
> 
> I will followup with Tony.

Hi Paul,

Just in case you are interested I have uploaded toolchains to here:

  http://shorne.noip.me/crosstool/files/bin/x86_64/5.4.0/

I will be sending the same (the files/patches dir) to Tony.

Re: linux-next: Tree for Jan 19

[Paul Gortmaker]

[Re: linux-next: Tree for Jan 19] On 26/01/2017 (Thu 06:22) Guenter Roeck wrote:

> On 01/25/2017 09:38 PM, Stafford Horne wrote:
> >On Wed, Jan 25, 2017 at 08:54:53PM -0800, Guenter Roeck wrote:
> >>On 01/25/2017 08:37 AM, Paul Gortmaker wrote:
> >>>[Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne 
> >>>wrote:
> >>>
> >>>[...]
> >>>
> >>>>
> >>>>Are all of these builds using the tests from lkp-tests [0]?
> >>>
> >>>Not using any specific tests, other than compiling allmodconfig and
> >>>defconfig.
> >>>
> >>>>
> >>>>If so and no one is working on openrisc toolchain updates I will package 
> >>>>up
> >>>>a modern toolchain for the cdn [1] and send patches for lkp-test.
> >>>>
> >>>>If there is something else that needs to be done let me know.
> >>>>
> >>>>[0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> >>>>[1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/
> >>>
> >>>If you could work with Tony (his email is at the bottom of the crosstool
> >>>front page in [1]) to get the or32 binutils updated, that would be
> >>>great.  With all the arch currrently in linux, I pretty much have to
> >>>just use what is available from kernel.org as prebuilts.
> >>>
> >>
> >>Different problem, but from the 0day info I thought you might be interested
> >>in the following breakage as well (seen in -next).
> >>
> >>/opt/buildbot/slave/next-next/build/arch/score/kernel/traps.c: In function 
> >>'do_adedata':
> >>/opt/buildbot/slave/next-next/build/arch/score/kernel/traps.c:185:2: error: 
> >>implicit declaration of function 'search_exception_tables'
> >>
> >>Reported on kerneltests.org.
> >
> >Thanks Guenter,
> >
> >Is this for me of Paul?
> >
> Paul, sorry.

Thanks for the heads up.  I'll make an appropriate addition to the score
patch.  Odd that I didn't see a mail from the 0day bot.

Paul.
--

> 
> Guenter
> 

Re: linux-next: Tree for Jan 19

[Paul Gortmaker]

[Re: linux-next: Tree for Jan 19] On 26/01/2017 (Thu 06:22) Guenter Roeck wrote:

> On 01/25/2017 09:38 PM, Stafford Horne wrote:
> >On Wed, Jan 25, 2017 at 08:54:53PM -0800, Guenter Roeck wrote:
> >>On 01/25/2017 08:37 AM, Paul Gortmaker wrote:
> >>>[Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne 
> >>>wrote:
> >>>
> >>>[...]
> >>>
> >>>>
> >>>>Are all of these builds using the tests from lkp-tests [0]?
> >>>
> >>>Not using any specific tests, other than compiling allmodconfig and
> >>>defconfig.
> >>>
> >>>>
> >>>>If so and no one is working on openrisc toolchain updates I will package 
> >>>>up
> >>>>a modern toolchain for the cdn [1] and send patches for lkp-test.
> >>>>
> >>>>If there is something else that needs to be done let me know.
> >>>>
> >>>>[0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> >>>>[1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/
> >>>
> >>>If you could work with Tony (his email is at the bottom of the crosstool
> >>>front page in [1]) to get the or32 binutils updated, that would be
> >>>great.  With all the arch currrently in linux, I pretty much have to
> >>>just use what is available from kernel.org as prebuilts.
> >>>
> >>
> >>Different problem, but from the 0day info I thought you might be interested
> >>in the following breakage as well (seen in -next).
> >>
> >>/opt/buildbot/slave/next-next/build/arch/score/kernel/traps.c: In function 
> >>'do_adedata':
> >>/opt/buildbot/slave/next-next/build/arch/score/kernel/traps.c:185:2: error: 
> >>implicit declaration of function 'search_exception_tables'
> >>
> >>Reported on kerneltests.org.
> >
> >Thanks Guenter,
> >
> >Is this for me of Paul?
> >
> Paul, sorry.

Thanks for the heads up.  I'll make an appropriate addition to the score
patch.  Odd that I didn't see a mail from the 0day bot.

Paul.
--

> 
> Guenter
> 

Re: linux-next: Tree for Jan 19

[Guenter Roeck]

On 01/25/2017 09:38 PM, Stafford Horne wrote:

On Wed, Jan 25, 2017 at 08:54:53PM -0800, Guenter Roeck wrote:

On 01/25/2017 08:37 AM, Paul Gortmaker wrote:

[Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne 
wrote:

[...]



Are all of these builds using the tests from lkp-tests [0]?


Not using any specific tests, other than compiling allmodconfig and
defconfig.



If so and no one is working on openrisc toolchain updates I will package up
a modern toolchain for the cdn [1] and send patches for lkp-test.

If there is something else that needs to be done let me know.

[0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
[1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/


If you could work with Tony (his email is at the bottom of the crosstool
front page in [1]) to get the or32 binutils updated, that would be
great.  With all the arch currrently in linux, I pretty much have to
just use what is available from kernel.org as prebuilts.



Different problem, but from the 0day info I thought you might be interested
in the following breakage as well (seen in -next).

/opt/buildbot/slave/next-next/build/arch/score/kernel/traps.c: In function 
'do_adedata':
/opt/buildbot/slave/next-next/build/arch/score/kernel/traps.c:185:2: error: 
implicit declaration of function 'search_exception_tables'

Reported on kerneltests.org.


Thanks Guenter,

Is this for me of Paul?


Paul, sorry.

Guenter

Re: linux-next: Tree for Jan 19

[Guenter Roeck]

On 01/25/2017 09:38 PM, Stafford Horne wrote:

On Wed, Jan 25, 2017 at 08:54:53PM -0800, Guenter Roeck wrote:

On 01/25/2017 08:37 AM, Paul Gortmaker wrote:

[Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne 
wrote:

[...]



Are all of these builds using the tests from lkp-tests [0]?


Not using any specific tests, other than compiling allmodconfig and
defconfig.



If so and no one is working on openrisc toolchain updates I will package up
a modern toolchain for the cdn [1] and send patches for lkp-test.

If there is something else that needs to be done let me know.

[0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
[1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/


If you could work with Tony (his email is at the bottom of the crosstool
front page in [1]) to get the or32 binutils updated, that would be
great.  With all the arch currrently in linux, I pretty much have to
just use what is available from kernel.org as prebuilts.



Different problem, but from the 0day info I thought you might be interested
in the following breakage as well (seen in -next).

/opt/buildbot/slave/next-next/build/arch/score/kernel/traps.c: In function 
'do_adedata':
/opt/buildbot/slave/next-next/build/arch/score/kernel/traps.c:185:2: error: 
implicit declaration of function 'search_exception_tables'

Reported on kerneltests.org.


Thanks Guenter,

Is this for me of Paul?


Paul, sorry.

Guenter

Re: linux-next: Tree for Jan 19

[Stafford Horne]

On Wed, Jan 25, 2017 at 11:37:11AM -0500, Paul Gortmaker wrote:
> [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne 
> wrote:
> 
> [...]
> 
> > 
> > Are all of these builds using the tests from lkp-tests [0]?
> 
> Not using any specific tests, other than compiling allmodconfig and
> defconfig.
> 
> > 
> > If so and no one is working on openrisc toolchain updates I will package up
> > a modern toolchain for the cdn [1] and send patches for lkp-test.
> > 
> > If there is something else that needs to be done let me know.
> > 
> > [0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> > [1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/
> 
> If you could work with Tony (his email is at the bottom of the crosstool
> front page in [1]) to get the or32 binutils updated, that would be
> great.  With all the arch currrently in linux, I pretty much have to
> just use what is available from kernel.org as prebuilts.
> 

Thanks,

I will followup with Tony.

Re: linux-next: Tree for Jan 19

[Stafford Horne]

On Wed, Jan 25, 2017 at 11:37:11AM -0500, Paul Gortmaker wrote:
> [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne 
> wrote:
> 
> [...]
> 
> > 
> > Are all of these builds using the tests from lkp-tests [0]?
> 
> Not using any specific tests, other than compiling allmodconfig and
> defconfig.
> 
> > 
> > If so and no one is working on openrisc toolchain updates I will package up
> > a modern toolchain for the cdn [1] and send patches for lkp-test.
> > 
> > If there is something else that needs to be done let me know.
> > 
> > [0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> > [1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/
> 
> If you could work with Tony (his email is at the bottom of the crosstool
> front page in [1]) to get the or32 binutils updated, that would be
> great.  With all the arch currrently in linux, I pretty much have to
> just use what is available from kernel.org as prebuilts.
> 

Thanks,

I will followup with Tony.

Re: linux-next: Tree for Jan 19

[Stafford Horne]

On Wed, Jan 25, 2017 at 08:54:53PM -0800, Guenter Roeck wrote:
> On 01/25/2017 08:37 AM, Paul Gortmaker wrote:
> > [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne 
> > wrote:
> > 
> > [...]
> > 
> > > 
> > > Are all of these builds using the tests from lkp-tests [0]?
> > 
> > Not using any specific tests, other than compiling allmodconfig and
> > defconfig.
> > 
> > > 
> > > If so and no one is working on openrisc toolchain updates I will package 
> > > up
> > > a modern toolchain for the cdn [1] and send patches for lkp-test.
> > > 
> > > If there is something else that needs to be done let me know.
> > > 
> > > [0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> > > [1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/
> > 
> > If you could work with Tony (his email is at the bottom of the crosstool
> > front page in [1]) to get the or32 binutils updated, that would be
> > great.  With all the arch currrently in linux, I pretty much have to
> > just use what is available from kernel.org as prebuilts.
> > 
> 
> Different problem, but from the 0day info I thought you might be interested
> in the following breakage as well (seen in -next).
> 
> /opt/buildbot/slave/next-next/build/arch/score/kernel/traps.c: In function 
> 'do_adedata':
> /opt/buildbot/slave/next-next/build/arch/score/kernel/traps.c:185:2: error: 
> implicit declaration of function 'search_exception_tables'
> 
> Reported on kerneltests.org.

Thanks Guenter,

Is this for me of Paul?

You reported score above, but I think probably this is also impacting
openrisc.

Anyway,
I think this is due to Puals changes which separated out extable from
module.  traps.c in score and openrisc use search_exception_tables and
include  to get it.

I did see Paul post a patch to fix traps.c too,

This should be fixed by today.

-Stafford

Re: linux-next: Tree for Jan 19

[Stafford Horne]

On Wed, Jan 25, 2017 at 08:54:53PM -0800, Guenter Roeck wrote:
> On 01/25/2017 08:37 AM, Paul Gortmaker wrote:
> > [Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne 
> > wrote:
> > 
> > [...]
> > 
> > > 
> > > Are all of these builds using the tests from lkp-tests [0]?
> > 
> > Not using any specific tests, other than compiling allmodconfig and
> > defconfig.
> > 
> > > 
> > > If so and no one is working on openrisc toolchain updates I will package 
> > > up
> > > a modern toolchain for the cdn [1] and send patches for lkp-test.
> > > 
> > > If there is something else that needs to be done let me know.
> > > 
> > > [0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> > > [1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/
> > 
> > If you could work with Tony (his email is at the bottom of the crosstool
> > front page in [1]) to get the or32 binutils updated, that would be
> > great.  With all the arch currrently in linux, I pretty much have to
> > just use what is available from kernel.org as prebuilts.
> > 
> 
> Different problem, but from the 0day info I thought you might be interested
> in the following breakage as well (seen in -next).
> 
> /opt/buildbot/slave/next-next/build/arch/score/kernel/traps.c: In function 
> 'do_adedata':
> /opt/buildbot/slave/next-next/build/arch/score/kernel/traps.c:185:2: error: 
> implicit declaration of function 'search_exception_tables'
> 
> Reported on kerneltests.org.

Thanks Guenter,

Is this for me of Paul?

You reported score above, but I think probably this is also impacting
openrisc.

Anyway,
I think this is due to Puals changes which separated out extable from
module.  traps.c in score and openrisc use search_exception_tables and
include  to get it.

I did see Paul post a patch to fix traps.c too,

This should be fixed by today.

-Stafford

Re: linux-next: Tree for Jan 19

[Guenter Roeck]

On 01/25/2017 08:37 AM, Paul Gortmaker wrote:

[Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne 
wrote:

[...]



Are all of these builds using the tests from lkp-tests [0]?


Not using any specific tests, other than compiling allmodconfig and
defconfig.



If so and no one is working on openrisc toolchain updates I will package up
a modern toolchain for the cdn [1] and send patches for lkp-test.

If there is something else that needs to be done let me know.

[0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
[1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/


If you could work with Tony (his email is at the bottom of the crosstool
front page in [1]) to get the or32 binutils updated, that would be
great.  With all the arch currrently in linux, I pretty much have to
just use what is available from kernel.org as prebuilts.



Different problem, but from the 0day info I thought you might be interested
in the following breakage as well (seen in -next).

/opt/buildbot/slave/next-next/build/arch/score/kernel/traps.c: In function 
'do_adedata':
/opt/buildbot/slave/next-next/build/arch/score/kernel/traps.c:185:2: error: 
implicit declaration of function 'search_exception_tables'

Reported on kerneltests.org.

Guenter

Re: linux-next: Tree for Jan 19

[Guenter Roeck]

On 01/25/2017 08:37 AM, Paul Gortmaker wrote:

[Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne 
wrote:

[...]



Are all of these builds using the tests from lkp-tests [0]?


Not using any specific tests, other than compiling allmodconfig and
defconfig.



If so and no one is working on openrisc toolchain updates I will package up
a modern toolchain for the cdn [1] and send patches for lkp-test.

If there is something else that needs to be done let me know.

[0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
[1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/


If you could work with Tony (his email is at the bottom of the crosstool
front page in [1]) to get the or32 binutils updated, that would be
great.  With all the arch currrently in linux, I pretty much have to
just use what is available from kernel.org as prebuilts.



Different problem, but from the 0day info I thought you might be interested
in the following breakage as well (seen in -next).

/opt/buildbot/slave/next-next/build/arch/score/kernel/traps.c: In function 
'do_adedata':
/opt/buildbot/slave/next-next/build/arch/score/kernel/traps.c:185:2: error: 
implicit declaration of function 'search_exception_tables'

Reported on kerneltests.org.

Guenter

Re: linux-next: Tree for Jan 19

[Paul Gortmaker]

[Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne 
wrote:

[...]

> 
> Are all of these builds using the tests from lkp-tests [0]?

Not using any specific tests, other than compiling allmodconfig and
defconfig.

> 
> If so and no one is working on openrisc toolchain updates I will package up
> a modern toolchain for the cdn [1] and send patches for lkp-test.
> 
> If there is something else that needs to be done let me know.
> 
> [0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> [1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/

If you could work with Tony (his email is at the bottom of the crosstool
front page in [1]) to get the or32 binutils updated, that would be
great.  With all the arch currrently in linux, I pretty much have to
just use what is available from kernel.org as prebuilts.

Paul.
--

> 
> -Stafford

Re: linux-next: Tree for Jan 19

[Paul Gortmaker]

[Re: linux-next: Tree for Jan 19] On 23/01/2017 (Mon 23:11) Stafford Horne 
wrote:

[...]

> 
> Are all of these builds using the tests from lkp-tests [0]?

Not using any specific tests, other than compiling allmodconfig and
defconfig.

> 
> If so and no one is working on openrisc toolchain updates I will package up
> a modern toolchain for the cdn [1] and send patches for lkp-test.
> 
> If there is something else that needs to be done let me know.
> 
> [0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> [1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/

If you could work with Tony (his email is at the bottom of the crosstool
front page in [1]) to get the or32 binutils updated, that would be
great.  With all the arch currrently in linux, I pretty much have to
just use what is available from kernel.org as prebuilts.

Paul.
--

> 
> -Stafford

Re: linux-next: Tree for Jan 19

[Stafford Horne]

On Thu, Jan 19, 2017 at 11:42:45AM -0500, Paul Gortmaker wrote:
> On Thu, Jan 19, 2017 at 12:39 AM, Stephen Rothwell  
> wrote:
> > Hi all,
> >
> > Changes since 20170118:
> >
> > The audit tree gained a conflict against Linus' tree.
> >
> > The tip tree gained a conflict against the security tree.
> >
> > The rcu tree gained a semantic conflict against the net-next tree for
> > which I applied a merge fix patch.
> >
> > I dropped 4 patches from the akpm tree that turned up in the tip tree.
> >
> > Non-merge commits (relative to Linus' tree): 3931
> >  4740 files changed, 146960 insertions(+), 87918 deletions(-)
> >
> 
> The or32 builds started failing in the last couple days:
> 
> http://kisskb.ellerman.id.au/kisskb/buildresult/12912013/
> 
> I was able to reproduce it locally, and a mindless bisect says:
> 
> 116ded1356614cff3facc9010125b5a28718cbf1 is the first bad commit
> commit 116ded1356614cff3facc9010125b5a28718cbf1
> Author: Stefan Kristiansson 
> Date:   Mon May 12 14:08:26 2014 +0300
> 
> openrisc: add atomic bitops
> 
> I expect the binutils sfr is using is probably similar vintage to
> what I've got here locally - from kernel.org crosstool stuff:
> 
> $ or32-linux-as --version
> GNU assembler (GNU Binutils) 2.20.1.20100303
> Copyright 2009 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License version 3 or later.
> This program has absolutely no warranty.
> This assembler was configured for a target of `or32-linux'.
> 

Are all of these builds using the tests from lkp-tests [0]?

If so and no one is working on openrisc toolchain updates I will package up
a modern toolchain for the cdn [1] and send patches for lkp-test.

If there is something else that needs to be done let me know.

[0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
[1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/

-Stafford

Re: linux-next: Tree for Jan 19

[Stafford Horne]

On Thu, Jan 19, 2017 at 11:42:45AM -0500, Paul Gortmaker wrote:
> On Thu, Jan 19, 2017 at 12:39 AM, Stephen Rothwell  
> wrote:
> > Hi all,
> >
> > Changes since 20170118:
> >
> > The audit tree gained a conflict against Linus' tree.
> >
> > The tip tree gained a conflict against the security tree.
> >
> > The rcu tree gained a semantic conflict against the net-next tree for
> > which I applied a merge fix patch.
> >
> > I dropped 4 patches from the akpm tree that turned up in the tip tree.
> >
> > Non-merge commits (relative to Linus' tree): 3931
> >  4740 files changed, 146960 insertions(+), 87918 deletions(-)
> >
> 
> The or32 builds started failing in the last couple days:
> 
> http://kisskb.ellerman.id.au/kisskb/buildresult/12912013/
> 
> I was able to reproduce it locally, and a mindless bisect says:
> 
> 116ded1356614cff3facc9010125b5a28718cbf1 is the first bad commit
> commit 116ded1356614cff3facc9010125b5a28718cbf1
> Author: Stefan Kristiansson 
> Date:   Mon May 12 14:08:26 2014 +0300
> 
> openrisc: add atomic bitops
> 
> I expect the binutils sfr is using is probably similar vintage to
> what I've got here locally - from kernel.org crosstool stuff:
> 
> $ or32-linux-as --version
> GNU assembler (GNU Binutils) 2.20.1.20100303
> Copyright 2009 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License version 3 or later.
> This program has absolutely no warranty.
> This assembler was configured for a target of `or32-linux'.
> 

Are all of these builds using the tests from lkp-tests [0]?

If so and no one is working on openrisc toolchain updates I will package up
a modern toolchain for the cdn [1] and send patches for lkp-test.

If there is something else that needs to be done let me know.

[0] git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
[1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.1/

-Stafford

Re: linux-next: Tree for Jan 19

[Stafford Horne]

Hi Paul,

On Thu, Jan 19, 2017 at 11:42:45AM -0500, Paul Gortmaker wrote:
> On Thu, Jan 19, 2017 at 12:39 AM, Stephen Rothwell  
> wrote:
> > Hi all,
> >
> > Changes since 20170118:
> >
> > The audit tree gained a conflict against Linus' tree.
> >
> > The tip tree gained a conflict against the security tree.
> >
> > The rcu tree gained a semantic conflict against the net-next tree for
> > which I applied a merge fix patch.
> >
> > I dropped 4 patches from the akpm tree that turned up in the tip tree.
> >
> > Non-merge commits (relative to Linus' tree): 3931
> >  4740 files changed, 146960 insertions(+), 87918 deletions(-)
> >
> 
> The or32 builds started failing in the last couple days:
> 
> http://kisskb.ellerman.id.au/kisskb/buildresult/12912013/
> 
> I was able to reproduce it locally, and a mindless bisect says:
> 
> 116ded1356614cff3facc9010125b5a28718cbf1 is the first bad commit
> commit 116ded1356614cff3facc9010125b5a28718cbf1
> Author: Stefan Kristiansson 
> Date:   Mon May 12 14:08:26 2014 +0300
> 
> openrisc: add atomic bitops
> 
> I expect the binutils sfr is using is probably similar vintage to
> what I've got here locally - from kernel.org crosstool stuff:
> 
> $ or32-linux-as --version
> GNU assembler (GNU Binutils) 2.20.1.20100303
> Copyright 2009 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License version 3 or later.
> This program has absolutely no warranty.
> This assembler was configured for a target of `or32-linux'.

I put a note on this in reply to previous build failures and also on the
patch series. This indroduces some recent instructions (2 years old) for
handling atomic memory load stores.

Sorry, I wasn't sure who all to notify.

TOOLCHAIN

These are likely due to the lwa/swa instructions.  A toolchain from the
last 2 years would be needed to build these instructions.  Can I suggest
that the test chain be updated?  I would suggest musl. But there are
currently two options openrisc team is maintaining.

The l.swa/l.lwa atomic memory operations were added to the openrisc spec
2 years back. These are the first kernel patches to use them.

:: or1k-musl-linux- chain ::

Get it here:
https://github.com/openrisc/or1k-gcc/tree/musl-5.4.0/gcc
  - build using
https://github.com/openrisc/musl-cross

OR

:: or1k-elf- chain ::

Get it here:
  https://github.com/openrisc/or1k-gcc/tree/or1k-5.4.0/gcc
  - build using baremetal/newlib
https://github.com/openrisc/newlib
  - instructions
http://openrisc.io/newlib/building.html


QEMU

The l.swa and l.lwa emulation is broken in qemu openrisc port. I have
sent patches [1] to qemu-devel to fix the qemu issues.

 [1] lists.nongnu.org/archive/html/qemu-devel/2017-01/msg02764.html


-Stafford

Re: linux-next: Tree for Jan 19

[Stafford Horne]

Hi Paul,

On Thu, Jan 19, 2017 at 11:42:45AM -0500, Paul Gortmaker wrote:
> On Thu, Jan 19, 2017 at 12:39 AM, Stephen Rothwell  
> wrote:
> > Hi all,
> >
> > Changes since 20170118:
> >
> > The audit tree gained a conflict against Linus' tree.
> >
> > The tip tree gained a conflict against the security tree.
> >
> > The rcu tree gained a semantic conflict against the net-next tree for
> > which I applied a merge fix patch.
> >
> > I dropped 4 patches from the akpm tree that turned up in the tip tree.
> >
> > Non-merge commits (relative to Linus' tree): 3931
> >  4740 files changed, 146960 insertions(+), 87918 deletions(-)
> >
> 
> The or32 builds started failing in the last couple days:
> 
> http://kisskb.ellerman.id.au/kisskb/buildresult/12912013/
> 
> I was able to reproduce it locally, and a mindless bisect says:
> 
> 116ded1356614cff3facc9010125b5a28718cbf1 is the first bad commit
> commit 116ded1356614cff3facc9010125b5a28718cbf1
> Author: Stefan Kristiansson 
> Date:   Mon May 12 14:08:26 2014 +0300
> 
> openrisc: add atomic bitops
> 
> I expect the binutils sfr is using is probably similar vintage to
> what I've got here locally - from kernel.org crosstool stuff:
> 
> $ or32-linux-as --version
> GNU assembler (GNU Binutils) 2.20.1.20100303
> Copyright 2009 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License version 3 or later.
> This program has absolutely no warranty.
> This assembler was configured for a target of `or32-linux'.

I put a note on this in reply to previous build failures and also on the
patch series. This indroduces some recent instructions (2 years old) for
handling atomic memory load stores.

Sorry, I wasn't sure who all to notify.

TOOLCHAIN

These are likely due to the lwa/swa instructions.  A toolchain from the
last 2 years would be needed to build these instructions.  Can I suggest
that the test chain be updated?  I would suggest musl. But there are
currently two options openrisc team is maintaining.

The l.swa/l.lwa atomic memory operations were added to the openrisc spec
2 years back. These are the first kernel patches to use them.

:: or1k-musl-linux- chain ::

Get it here:
https://github.com/openrisc/or1k-gcc/tree/musl-5.4.0/gcc
  - build using
https://github.com/openrisc/musl-cross

OR

:: or1k-elf- chain ::

Get it here:
  https://github.com/openrisc/or1k-gcc/tree/or1k-5.4.0/gcc
  - build using baremetal/newlib
https://github.com/openrisc/newlib
  - instructions
http://openrisc.io/newlib/building.html


QEMU

The l.swa and l.lwa emulation is broken in qemu openrisc port. I have
sent patches [1] to qemu-devel to fix the qemu issues.

 [1] lists.nongnu.org/archive/html/qemu-devel/2017-01/msg02764.html


-Stafford

Re: linux-next: Tree for Jan 19

[Paul Gortmaker]

On Thu, Jan 19, 2017 at 12:39 AM, Stephen Rothwell  
wrote:
> Hi all,
>
> Changes since 20170118:
>
> The audit tree gained a conflict against Linus' tree.
>
> The tip tree gained a conflict against the security tree.
>
> The rcu tree gained a semantic conflict against the net-next tree for
> which I applied a merge fix patch.
>
> I dropped 4 patches from the akpm tree that turned up in the tip tree.
>
> Non-merge commits (relative to Linus' tree): 3931
>  4740 files changed, 146960 insertions(+), 87918 deletions(-)
>

The or32 builds started failing in the last couple days:

http://kisskb.ellerman.id.au/kisskb/buildresult/12912013/

I was able to reproduce it locally, and a mindless bisect says:

116ded1356614cff3facc9010125b5a28718cbf1 is the first bad commit
commit 116ded1356614cff3facc9010125b5a28718cbf1
Author: Stefan Kristiansson 
Date:   Mon May 12 14:08:26 2014 +0300

openrisc: add atomic bitops

I expect the binutils sfr is using is probably similar vintage to
what I've got here locally - from kernel.org crosstool stuff:

$ or32-linux-as --version
GNU assembler (GNU Binutils) 2.20.1.20100303
Copyright 2009 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or later.
This program has absolutely no warranty.
This assembler was configured for a target of `or32-linux'.

Paul.
--

Re: linux-next: Tree for Jan 19

[Paul Gortmaker]

On Thu, Jan 19, 2017 at 12:39 AM, Stephen Rothwell  
wrote:
> Hi all,
>
> Changes since 20170118:
>
> The audit tree gained a conflict against Linus' tree.
>
> The tip tree gained a conflict against the security tree.
>
> The rcu tree gained a semantic conflict against the net-next tree for
> which I applied a merge fix patch.
>
> I dropped 4 patches from the akpm tree that turned up in the tip tree.
>
> Non-merge commits (relative to Linus' tree): 3931
>  4740 files changed, 146960 insertions(+), 87918 deletions(-)
>

The or32 builds started failing in the last couple days:

http://kisskb.ellerman.id.au/kisskb/buildresult/12912013/

I was able to reproduce it locally, and a mindless bisect says:

116ded1356614cff3facc9010125b5a28718cbf1 is the first bad commit
commit 116ded1356614cff3facc9010125b5a28718cbf1
Author: Stefan Kristiansson 
Date:   Mon May 12 14:08:26 2014 +0300

openrisc: add atomic bitops

I expect the binutils sfr is using is probably similar vintage to
what I've got here locally - from kernel.org crosstool stuff:

$ or32-linux-as --version
GNU assembler (GNU Binutils) 2.20.1.20100303
Copyright 2009 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or later.
This program has absolutely no warranty.
This assembler was configured for a target of `or32-linux'.

Paul.
--

linux-next: Tree for Jan 19

[Stephen Rothwell]

Hi all,

Changes since 20170118:

The audit tree gained a conflict against Linus' tree.

The tip tree gained a conflict against the security tree.

The rcu tree gained a semantic conflict against the net-next tree for
which I applied a merge fix patch.

I dropped 4 patches from the akpm tree that turned up in the tip tree.

Non-merge commits (relative to Linus' tree): 3931
 4740 files changed, 146960 insertions(+), 87918 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
and pseries_le_defconfig and i386, sparc and sparc64 defconfig.

Below is a summary of the state of the merge.

I am currently merging 251 trees (counting Linus' and 36 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 (fa19a769f82f Merge branch 'fixes' of 
git://git.armlinux.org.uk/~rmk/linux-arm)
Merging fixes/master (30066ce675d3 Merge branch 'linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6)
Merging kbuild-current/rc-fixes (c7858bf16c0b asm-prototypes: Clear any CPP 
defines before declaring the functions)
Merging arc-current/for-curr (eb1357d942e5 ARC: module: Fix 
!CONFIG_ARC_DW2_UNWIND builds)
Merging arm-current/fixes (90f92c631b21 ARM: 8613/1: Fix the uaccess crash on 
PB11MPCore)
Merging m68k-current/for-linus (ad595b77c4a8 m68k/atari: Use seq_puts() in 
atari_get_hardware_list())
Merging metag-fixes/fixes (35d04077ad96 metag: Only define 
atomic_dec_if_positive conditionally)
Merging powerpc-fixes/fixes (27593d72c4ad powerpc/perf: Use MSR to report 
privilege level on P9 DD1)
Merging sparc/master (5d0e7705774d sparc: Fixed typo in sstate.c. Replaced 
panicing with panicking)
Merging fscrypt-current/for-stable (42d97eb0ade3 fscrypt: fix renaming and 
linking special files)
Merging net/master (d407bd25a204 bpf: don't trigger OOM killer under pressure 
with map alloc)
Merging ipsec/master (4e5da369df64 Documentation/networking: fix typo in 
mpls-sysctl)
Merging netfilter/master (3fd0b634de7d netfilter: ipt_CLUSTERIP: fix build 
error without procfs)
Merging ipvs/master (045169816b31 Merge branch 'linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6)
Merging wireless-drivers/master (7195439d1d71 Revert "bcma: init serial console 
directly from ChipCommon code")
Merging mac80211/master (dbef53621116 mac80211: prevent skb/txq mismatch)
Merging sound-current/for-linus (6cf4569ce356 Merge tag 'asoc-fix-v4.10-rc3' of 
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus)
Merging pci-current/for-linus (ea2a7fb12093 Revert "PCI: Add runtime PM support 
for PCIe ports")
Merging driver-core.current/driver-core-linus (49def1853334 Linux 4.10-rc4)
Merging tty.current/tty-linus (49def1853334 Linux 4.10-rc4)
Merging usb.current/usb-linus (833674a45ec7 Merge tag 'fixes-for-v4.10-rc5' of 
git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-linus)
Merging usb-gadget-fixes/fixes (efe357f4633a usb: dwc2: host: fix 
Wmaybe-uninitialized warning)
Merging usb-serial-fixes/usb-linus (49def1853334 Linux 4.10-rc4)
Merging usb-chipidea-fixes/ci-for-usb-stable (c7fbb09b2ea1 usb: chipidea: move 
the lock initialization to core file)
Merging phy/fixes (7ce7d89f4883 Linux 4.10-rc1)
Merging staging.current/staging-linus (a121103c9228 Linux 4.10-rc3)
Merging char-misc.current/char-misc-linus (49def1853334 Linux 4.10-rc4)
Merging input-current/for-linus (1c3415a06b10 Input: elants_i2c - avoid divide 
by 0 errors on bad touchscreen data)
Merging crypto-current/master (07825f0acd85 crypto: aesni - Fix 

linux-next: Tree for Jan 19

[Stephen Rothwell]

Hi all,

Changes since 20170118:

The audit tree gained a conflict against Linus' tree.

The tip tree gained a conflict against the security tree.

The rcu tree gained a semantic conflict against the net-next tree for
which I applied a merge fix patch.

I dropped 4 patches from the akpm tree that turned up in the tip tree.

Non-merge commits (relative to Linus' tree): 3931
 4740 files changed, 146960 insertions(+), 87918 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
and pseries_le_defconfig and i386, sparc and sparc64 defconfig.

Below is a summary of the state of the merge.

I am currently merging 251 trees (counting Linus' and 36 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 (fa19a769f82f Merge branch 'fixes' of 
git://git.armlinux.org.uk/~rmk/linux-arm)
Merging fixes/master (30066ce675d3 Merge branch 'linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6)
Merging kbuild-current/rc-fixes (c7858bf16c0b asm-prototypes: Clear any CPP 
defines before declaring the functions)
Merging arc-current/for-curr (eb1357d942e5 ARC: module: Fix 
!CONFIG_ARC_DW2_UNWIND builds)
Merging arm-current/fixes (90f92c631b21 ARM: 8613/1: Fix the uaccess crash on 
PB11MPCore)
Merging m68k-current/for-linus (ad595b77c4a8 m68k/atari: Use seq_puts() in 
atari_get_hardware_list())
Merging metag-fixes/fixes (35d04077ad96 metag: Only define 
atomic_dec_if_positive conditionally)
Merging powerpc-fixes/fixes (27593d72c4ad powerpc/perf: Use MSR to report 
privilege level on P9 DD1)
Merging sparc/master (5d0e7705774d sparc: Fixed typo in sstate.c. Replaced 
panicing with panicking)
Merging fscrypt-current/for-stable (42d97eb0ade3 fscrypt: fix renaming and 
linking special files)
Merging net/master (d407bd25a204 bpf: don't trigger OOM killer under pressure 
with map alloc)
Merging ipsec/master (4e5da369df64 Documentation/networking: fix typo in 
mpls-sysctl)
Merging netfilter/master (3fd0b634de7d netfilter: ipt_CLUSTERIP: fix build 
error without procfs)
Merging ipvs/master (045169816b31 Merge branch 'linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6)
Merging wireless-drivers/master (7195439d1d71 Revert "bcma: init serial console 
directly from ChipCommon code")
Merging mac80211/master (dbef53621116 mac80211: prevent skb/txq mismatch)
Merging sound-current/for-linus (6cf4569ce356 Merge tag 'asoc-fix-v4.10-rc3' of 
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus)
Merging pci-current/for-linus (ea2a7fb12093 Revert "PCI: Add runtime PM support 
for PCIe ports")
Merging driver-core.current/driver-core-linus (49def1853334 Linux 4.10-rc4)
Merging tty.current/tty-linus (49def1853334 Linux 4.10-rc4)
Merging usb.current/usb-linus (833674a45ec7 Merge tag 'fixes-for-v4.10-rc5' of 
git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-linus)
Merging usb-gadget-fixes/fixes (efe357f4633a usb: dwc2: host: fix 
Wmaybe-uninitialized warning)
Merging usb-serial-fixes/usb-linus (49def1853334 Linux 4.10-rc4)
Merging usb-chipidea-fixes/ci-for-usb-stable (c7fbb09b2ea1 usb: chipidea: move 
the lock initialization to core file)
Merging phy/fixes (7ce7d89f4883 Linux 4.10-rc1)
Merging staging.current/staging-linus (a121103c9228 Linux 4.10-rc3)
Merging char-misc.current/char-misc-linus (49def1853334 Linux 4.10-rc4)
Merging input-current/for-linus (1c3415a06b10 Input: elants_i2c - avoid divide 
by 0 errors on bad touchscreen data)
Merging crypto-current/master (07825f0acd85 crypto: aesni - Fix 

linux-next: Tree for Jan 19

[Stephen Rothwell]

Hi all,

Changes since 20150116:

The i2c tree lost its build failure.

The net-next tree gained a build failure so I used the version from
next-20150116 for today.

The luto-misc tree gained a conflict against the tip tree.

The akpm-current tree gained two build failures for which I added fix
patches.

The akpm tree lost a patch that turned up elsewhere.

Non-merge commits (relative to Linus' tree): 3428
 3316 files changed, 110203 insertions(+), 57548 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 234 trees (counting Linus' and 32 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 (ec6f34e5b552 Linux 3.19-rc5)
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 (2d9ed7406fd2 ARM: 8255/1: perf: Prevent wraparound 
during overflow)
Merging m68k-current/for-linus (f27bd5bfeda5 m68k: Wire up execveat)
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 (a87e810f61b4 powerpc: Work around gcc bug in 
current_thread_info())
Merging sparc/master (66d0f7ec9f10 sparc32: destroy_context() and switch_mm() 
needs to disable interrupts.)
Merging net/master (2061dcd6bff8 net: sctp: fix race for one-to-many sockets in 
sendmsg's auto associate)
Merging ipsec/master (f855691975bb xfrm6: Fix the nexthdr offset in 
_decode_session6.)
Merging sound-current/for-linus (6455931186bf ALSA: usb-audio: Add mic volume 
fix quirk for Logitech Webcam C210)
Merging pci-current/for-linus (d63e2e1f3df9 sparc/PCI: Clip bridge windows to 
fit in upstream windows)
Merging wireless-drivers/master (781f51d4c203 Merge tag 
'iwlwifi-for-kalle-2015-01-13' of 
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes)
Merging driver-core.current/driver-core-linus (72392ed0eb6f kernfs: Fix 
kernfs_name_compare)
Merging tty.current/tty-linus (31ec77aca72e serial: samsung: Add the support 
for Exynos5433 SoC)
Merging usb.current/usb-linus (f8359dae68bd Merge tag 'fixes-for-v3.19-rc6' of 
git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-linus)
Merging usb-gadget-fixes/fixes (39e60635a015 usb: dwc3: gadget: Stop TRB 
preparation after limit is reached)
Merging usb-serial-fixes/usb-linus (04f9c6e6d175 usb: serial: handle -ENODEV 
quietly in generic_submit_read_urb)
Merging staging.current/staging-linus (a307d1d6d4cf staging: vt6655: fix sparse 
warning: argument type)
Merging char-misc.current/char-misc-linus (7b7c54914f73 mcb: mcb-pci: Only 
remap the 1st 0x200 bytes of BAR 0)
Merging input-current/for-linus (029b18361921 Input: uinput - fix ioctl nr 
overflow for UI_GET_SYSNAME/VERSION)
Merging md-current/for-linus (d47648fcf061 raid5: avoid finding "discard" 
stripe)
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 dwmw2/master (5950f0803ca9 pcmcia: remove RPX board stuff)
Merging devicetree-current/devicetree/merge (094cb98179f1 of/fdt: 
memblock_reserve /memreserve/ regions in the case of partial overlap)
Merging 

linux-next: Tree for Jan 19

[Stephen Rothwell]

Hi all,

Changes since 20150116:

The i2c tree lost its build failure.

The net-next tree gained a build failure so I used the version from
next-20150116 for today.

The luto-misc tree gained a conflict against the tip tree.

The akpm-current tree gained two build failures for which I added fix
patches.

The akpm tree lost a patch that turned up elsewhere.

Non-merge commits (relative to Linus' tree): 3428
 3316 files changed, 110203 insertions(+), 57548 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 234 trees (counting Linus' and 32 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 (ec6f34e5b552 Linux 3.19-rc5)
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 (2d9ed7406fd2 ARM: 8255/1: perf: Prevent wraparound 
during overflow)
Merging m68k-current/for-linus (f27bd5bfeda5 m68k: Wire up execveat)
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 (a87e810f61b4 powerpc: Work around gcc bug in 
current_thread_info())
Merging sparc/master (66d0f7ec9f10 sparc32: destroy_context() and switch_mm() 
needs to disable interrupts.)
Merging net/master (2061dcd6bff8 net: sctp: fix race for one-to-many sockets in 
sendmsg's auto associate)
Merging ipsec/master (f855691975bb xfrm6: Fix the nexthdr offset in 
_decode_session6.)
Merging sound-current/for-linus (6455931186bf ALSA: usb-audio: Add mic volume 
fix quirk for Logitech Webcam C210)
Merging pci-current/for-linus (d63e2e1f3df9 sparc/PCI: Clip bridge windows to 
fit in upstream windows)
Merging wireless-drivers/master (781f51d4c203 Merge tag 
'iwlwifi-for-kalle-2015-01-13' of 
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes)
Merging driver-core.current/driver-core-linus (72392ed0eb6f kernfs: Fix 
kernfs_name_compare)
Merging tty.current/tty-linus (31ec77aca72e serial: samsung: Add the support 
for Exynos5433 SoC)
Merging usb.current/usb-linus (f8359dae68bd Merge tag 'fixes-for-v3.19-rc6' of 
git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-linus)
Merging usb-gadget-fixes/fixes (39e60635a015 usb: dwc3: gadget: Stop TRB 
preparation after limit is reached)
Merging usb-serial-fixes/usb-linus (04f9c6e6d175 usb: serial: handle -ENODEV 
quietly in generic_submit_read_urb)
Merging staging.current/staging-linus (a307d1d6d4cf staging: vt6655: fix sparse 
warning: argument type)
Merging char-misc.current/char-misc-linus (7b7c54914f73 mcb: mcb-pci: Only 
remap the 1st 0x200 bytes of BAR 0)
Merging input-current/for-linus (029b18361921 Input: uinput - fix ioctl nr 
overflow for UI_GET_SYSNAME/VERSION)
Merging md-current/for-linus (d47648fcf061 raid5: avoid finding discard 
stripe)
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 dwmw2/master (5950f0803ca9 pcmcia: remove RPX board stuff)
Merging devicetree-current/devicetree/merge (094cb98179f1 of/fdt: 
memblock_reserve /memreserve/ regions in the case of partial overlap)
Merging