* Re: linux-next: Tree for Oct 26 (crypto/acompress.ko)
From: Giovanni Cabiddu @ 2016-10-27 5:17 UTC (permalink / raw)
To: Paul Gortmaker
Cc: Randy Dunlap, Stephen Rothwell, linux-next@vger.kernel.org, LKML,
linux-crypto, Herbert Xu
In-Reply-To: <CAP=VYLq=Zgaf5uhWVG68Hyha=gJ923ZkW+v7UsfsOJE53YxR0w@mail.gmail.com>
Hi,
On Wed, Oct 26, 2016 at 07:54:00PM -0400, Paul Gortmaker wrote:
> So, no EXPORT_SYMBOL, and any .config which has ACOMP2=m will fail.
I sent a patch for this:
https://patchwork.kernel.org/patch/9396503/
Regards,
--
Giovanni
^ permalink raw reply
* Re: linux-next: Tree for Oct 25
From: Daniel Vetter @ 2016-10-27 6:21 UTC (permalink / raw)
To: Paul Gortmaker
Cc: Stephen Rothwell, airlied, dri-devel, linux-next@vger.kernel.org,
LKML, zhi.a.wang
In-Reply-To: <CAP=VYLqdh2E17pZmEwQWS66Y9jdx-3SHsZkt5e4nitpg1N-A_g@mail.gmail.com>
On Tue, Oct 25, 2016 at 09:09:33PM -0400, Paul Gortmaker wrote:
> On Mon, Oct 24, 2016 at 11:31 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > Hi all,
> >
> > There will probably be no linux-next releases next week while I attend
> > the Kernel Summit.
> >
> > Changes since 20161024:
> >
> > The pm tree gained a conflict against the imx-mxs tree.
> >
> > The mali-dp tree gained a conflict against the drm-misc tree.
> >
> > The sunxi tree gained a build failure so I used the version from
> > next-20161024.
> >
> > The akpm-current tree still had its build failures for which I applied
> > 2 patches.
> >
> > Non-merge commits (relative to Linus' tree): 2174
> > 2622 files changed, 187829 insertions(+), 38953 deletions(-)
>
> The i386 allmodconfig fails with bad 32/64 math for about the last 5 days.
>
> ERROR: "__umoddi3" [drivers/gpu/drm/i915/i915.ko] undefined!
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/12840554/
>
> git bisect says:
>
> first bad commit: [4d60c5fd3f8751ea751d6dc6cfe0c1620420ccf8]
> drm/i915/gvt: vGPU PCI configuration space virtualization
>
> Authors/maintainers added to Cc/To list. Guessing folks weren't
> aware of the regression.
The fix is in-flight. Thanks anyway for the report.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply
* next-20161027 build: 0 failures 1 warnings (next-20161027)
From: Build bot for Mark Brown @ 2016-10-27 8:57 UTC (permalink / raw)
To: kernel-build-reports, linaro-kernel, linux-next
Tree/Branch: next-20161027
Git describe: next-20161027
Commit: 58308d9377 Add linux-next specific files for 20161027
Build Time: 154 min 22 sec
Passed: 10 / 10 (100.00 %)
Failed: 0 / 10 ( 0.00 %)
Errors: 0
Warnings: 1
Section Mismatches: 0
-------------------------------------------------------------------------------
defconfigs with issues (other than build errors):
1 warnings 0 mismatches : arm64-allmodconfig
-------------------------------------------------------------------------------
Warnings Summary: 1
1 ../include/linux/kernel.h:740:16: warning: comparison of distinct pointer types lacks a cast
===============================================================================
Detailed per-defconfig build reports below:
-------------------------------------------------------------------------------
arm64-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches
Warnings:
../include/linux/kernel.h:740:16: warning: comparison of distinct pointer types lacks a cast
-------------------------------------------------------------------------------
Passed with no errors, warnings or mismatches:
arm64-allnoconfig
arm-multi_v5_defconfig
arm-multi_v7_defconfig
x86_64-defconfig
arm-allmodconfig
arm-allnoconfig
x86_64-allnoconfig
arm-multi_v4t_defconfig
arm64-defconfig
close failed in file object destructor:
sys.excepthook is missing
lost sys.stderr
^ permalink raw reply
* Re: linux-next: bad commit in the sunxi tree
From: Maxime Ripard @ 2016-10-27 20:41 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-kernel
In-Reply-To: <20161027104225.4f0f2774@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]
Hi Stephen,
On Thu, Oct 27, 2016 at 10:42:25AM +1100, Stephen Rothwell wrote:
> Hi Maxime,
>
> On Tue, 25 Oct 2016 11:44:09 +0200 Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
> >
> > On Tue, Oct 25, 2016 at 09:22:55AM +1100, Stephen Rothwell wrote:
> > > Hi Maxime,
> > >
> > > In today's sunxi tree
> > > (git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git#sunxi/for-next)
> > > I noticed that commit
> > >
> > > 3861b711f8b5 ("ARM: sun5i: chip: add a node for the w1 gpio controller")
> > >
> > > has no Signed-off-by from its committer.
> >
> > Thanks, this has been fixed.
> >
> > Just out of curiosity, what command do you run to catch this?
>
> None :-) I look at the differences in each tree as I fetch it and
> just happen to notice some of these sometimes. I should have a git
> hook to check that there is a Signed-off-by for the author and
> committer, but I would have to invest some time to figure out how :-)
Ok, that's actually the real question I had in mind, if you had a hook
I could use in order to avoid that kind of things in the future :)
I guess I have a new item on my todo list.
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply
* linux-next: build warning in Linus' tree
From: Stephen Rothwell @ 2016-10-27 22:29 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-next, linux-kernel
Hi Linus,
Building your tree, today's linux-next build (powerpc ppc64_defconfig)
produced this warning:
mm/memory_hotplug.c: In function 'try_offline_node':
mm/memory_hotplug.c:2120:6: warning: unused variable 'i' [-Wunused-variable]
int i;
^
Introduced by commit
9dcb8b685fc3 ("mm: remove per-zone hashtable of bitlock waitqueues")
--
Cheers,
Stephen Rothwell
^ permalink raw reply
* Re: linux-next: build warning in Linus' tree
From: Linus Torvalds @ 2016-10-27 22:48 UTC (permalink / raw)
To: Stephen Rothwell, Andrey Ryabinin, Alexander Potapenko,
Dmitry Vyukov
Cc: linux-next, Linux Kernel Mailing List
In-Reply-To: <20161028092920.4d84f8f1@canb.auug.org.au>
On Thu, Oct 27, 2016 at 3:29 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Building your tree, today's linux-next build (powerpc ppc64_defconfig)
> produced this warning:
>
> mm/memory_hotplug.c: In function 'try_offline_node':
> mm/memory_hotplug.c:2120:6: warning: unused variable 'i' [-Wunused-variable]
> int i;
> ^
>
> Introduced by commit
>
> 9dcb8b685fc3 ("mm: remove per-zone hashtable of bitlock waitqueues")
Strange. I wonder why I didn't see that warning. Not with
allmodconfig, and not with my normal build.
[ Looks around ]
Hmm. Apparently "allmodconfig" doesn't actually enable memory hotplug.
And the reason is that allmodconfig enables KASAN, which then disables
MEMORY_HOTPLUG.
I wonder if we should make KASAN depend on !COMPILE_TEST, because it
does seem to disable a lot of build-time testing.
Oh well. I'll remove the stupid unused variable, thanks for the heads-up.
Linus
^ permalink raw reply
* Re: linux-next: build warning in Linus' tree
From: Linus Torvalds @ 2016-10-27 23:01 UTC (permalink / raw)
To: Stephen Rothwell, Andrey Ryabinin, Alexander Potapenko,
Dmitry Vyukov
Cc: linux-next, Linux Kernel Mailing List
In-Reply-To: <CA+55aFztZ1VuMhmx0_DX3ubrFNKcLTcW0OqDLRfxa0g2AeGY-w@mail.gmail.com>
On Thu, Oct 27, 2016 at 3:48 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> I wonder if we should make KASAN depend on !COMPILE_TEST, because it
> does seem to disable a lot of build-time testing.
Actually, we should probably just make the MEMORY_HOTPLUG dependency be
depends on COMPILE_TEST || !KASAN
since the memory-hotplug code should still *build* with KASAN, it just
doesn't work. That's exactly what the COMPILE_TEST config option is
there for - to get build coverage even for things that aren't
necessarily sane to run.
I'll do that, to get my build coverage up. I really expected my
allmodconfig builds to verify that I had removed the per-zone
waitqueue code completely, and I'm happy that the breakage was
apparently limited to that unused variable..
In the meantime, thanks for noticing and letting me know.
Linus
^ permalink raw reply
* Re: linux-next: build warning in Linus' tree
From: Alexander Potapenko @ 2016-10-27 23:05 UTC (permalink / raw)
To: Linus Torvalds
Cc: Stephen Rothwell, Andrey Ryabinin, Dmitry Vyukov, linux-next,
Linux Kernel Mailing List
In-Reply-To: <CA+55aFwDL2_Ecuei4tYLH34RDmOba_COfr5JajasvYXA++yUgA@mail.gmail.com>
On Thu, Oct 27, 2016 at 4:01 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Thu, Oct 27, 2016 at 3:48 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>>
>> I wonder if we should make KASAN depend on !COMPILE_TEST, because it
>> does seem to disable a lot of build-time testing.
>
> Actually, we should probably just make the MEMORY_HOTPLUG dependency be
>
> depends on COMPILE_TEST || !KASAN
Maybe we could just reverse the MEMORY_HOTPLUG->!KASAN dependency to
make it KASAN->!MEMORY_HOTPLUG?
Is it at all correct that allmodconfig enables KASAN? If/when we have
other compiler-based tools, which of them will allmodconfig pick?
> since the memory-hotplug code should still *build* with KASAN, it just
> doesn't work. That's exactly what the COMPILE_TEST config option is
> there for - to get build coverage even for things that aren't
> necessarily sane to run.
>
> I'll do that, to get my build coverage up. I really expected my
> allmodconfig builds to verify that I had removed the per-zone
> waitqueue code completely, and I'm happy that the breakage was
> apparently limited to that unused variable..
>
> In the meantime, thanks for noticing and letting me know.
>
> Linus
--
Alexander Potapenko
Software Engineer
Google Germany GmbH
Erika-Mann-Straße, 33
80636 München
Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
^ permalink raw reply
* Re: linux-next: build warning in Linus' tree
From: Linus Torvalds @ 2016-10-27 23:25 UTC (permalink / raw)
To: Alexander Potapenko
Cc: Stephen Rothwell, Andrey Ryabinin, Dmitry Vyukov, linux-next,
Linux Kernel Mailing List
In-Reply-To: <CAG_fn=WCvtf7yvj7JT5ahA21+P3F0Q==fqhS4e-3B=oRuPnVrA@mail.gmail.com>
On Thu, Oct 27, 2016 at 4:05 PM, Alexander Potapenko <glider@google.com> wrote:
>
> Maybe we could just reverse the MEMORY_HOTPLUG->!KASAN dependency to
> make it KASAN->!MEMORY_HOTPLUG?
Yes, that was my initial approach too, but then I decided that I'd
rather build-test both together anyway. Since I can. So that just gets
me the best of both worlds.
We've had issues like this before, and "make allmodconfig" will never
enable _everything_ (ie you always have to make some choices that will
disable other cases, if only for reasons like SLUB-vs-SLAB etc).
But in general the more coverage I get from build testing (without
having to do lots and lots of builds - that's what the build farms are
for after I have pushed things out), the better.
Linus
^ permalink raw reply
* linux-next: bad merge in the jc_docs tree
From: Stephen Rothwell @ 2016-10-27 23:30 UTC (permalink / raw)
To: Jonathan Corbet; +Cc: linux-next, linux-kernel
Hi Jon,
I noticed that you left some conflict markers in
Documentation/admin-guide/index.rst in merge commit
7a6992dc952e ("Merge branch 'doc-tweaks' into docs-next")
--
Cheers,
Stephen Rothwell
^ permalink raw reply
* Re: linux-next: build warning in Linus' tree
From: Stephen Rothwell @ 2016-10-27 23:40 UTC (permalink / raw)
To: Linus Torvalds
Cc: Andrey Ryabinin, Alexander Potapenko, Dmitry Vyukov, linux-next,
Linux Kernel Mailing List
In-Reply-To: <CA+55aFwDL2_Ecuei4tYLH34RDmOba_COfr5JajasvYXA++yUgA@mail.gmail.com>
Hi Linus,
On Thu, 27 Oct 2016 16:01:22 -0700 Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> In the meantime, thanks for noticing and letting me know.
It was pointed out by the extra checking you asked me to add in order
to easier detect new warnings for code added to linux-next :-)
--
Cheers,
Stephen Rothwell
^ permalink raw reply
* Re: linux-next: bad merge in the jc_docs tree
From: Jonathan Corbet @ 2016-10-27 23:50 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-kernel
In-Reply-To: <20161028103029.1e147f3e@canb.auug.org.au>
On Fri, 28 Oct 2016 10:30:29 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> I noticed that you left some conflict markers in
> Documentation/admin-guide/index.rst in merge commit
>
> 7a6992dc952e ("Merge branch 'doc-tweaks' into docs-next")
Argh. I noticed that too, but failed to amend the merge before pushing.
Thanks for the heads-up.
jon
^ permalink raw reply
* mmotm 2016-10-27-18-27 uploaded
From: akpm @ 2016-10-28 1:28 UTC (permalink / raw)
To: mm-commits, linux-kernel, linux-mm, linux-fsdevel, linux-next,
sfr, mhocko, broonie
The mm-of-the-moment snapshot 2016-10-27-18-27 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You will need quilt to apply these patches to the latest Linus release (4.x
or 4.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
http://ozlabs.org/~akpm/mmotm/series
The file broken-out.tar.gz contains two datestamp files: .DATE and
.DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
followed by the base kernel version against which this patch series is to
be applied.
This tree is partially included in linux-next. To see which patches are
included in linux-next, consult the `series' file. Only the patches
within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
linux-next.
A git tree which contains the memory management portion of this tree is
maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
by Michal Hocko. It contains the patches which are between the
"#NEXT_PATCHES_START mm" and "#NEXT_PATCHES_END" markers, from the series
file, http://www.ozlabs.org/~akpm/mmotm/series.
A full copy of the full kernel tree with the linux-next and mmotm patches
already applied is available through git within an hour of the mmotm
release. Individual mmotm releases are tagged. The master branch always
points to the latest release, so it's constantly rebasing.
http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/
To develop on top of mmotm git:
$ git remote add mmotm git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
$ git remote update mmotm
$ git checkout -b topic mmotm/master
<make changes, commit>
$ git send-email mmotm/master.. [...]
To rebase a branch with older patches to a new mmotm release:
$ git remote update mmotm
$ git rebase --onto mmotm/master <topic base> topic
The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second)
contains daily snapshots of the -mm tree. It is updated more frequently
than mmotm, and is untested.
A git copy of this tree is available at
http://git.cmpxchg.org/cgit.cgi/linux-mmots.git/
and use of this tree is similar to
http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/, described above.
This mmotm tree contains the following patches against 4.9-rc2:
(patches marked "*" will be included in linux-next)
origin.patch
* mm-slab-fix-kmemcg-cache-creation-delayed-issue.patch
* kcov-properly-check-if-we-are-in-an-interrupt.patch
* h8300-fix-syscall-restarting.patch
* mm-list_lruc-avoid-error-path-null-pointer-deref.patch
* mm-page_alloc-use-kern_cont-where-appropriate.patch
* mm-slab-improve-performance-of-gathering-slabinfo-stats.patch
* ipc-account-for-kmem-usage-on-mqueue-and-msg.patch
* kconfigh-remove-config_enabled-macro.patch
* latent_entropy-raise-config_frame_warn-by-default.patch
* lib-bump-stackdepot-capacity-from-16mb-to-128mb.patch
* mm-kmemleak-ensure-that-the-task-stack-is-not-freed-during-scanning.patch
* proc-fix-null-dereference-when-reading-proc-pid-auxv.patch
* credits-update-credit-information-for-martin-kepplinger.patch
* mm-memcontrol-do-not-recurse-in-direct-reclaim.patch
* lib-genallocc-start-search-from-start-of-chunk.patch
* fs-exofs-print-a-hex-number-after-a-0x-prefix.patch
* block-dac960-print-a-hex-number-after-a-0x-prefix.patch
* ipack-print-a-hex-number-after-a-0x-prefix.patch
* cris-arch-v32-cryptocop-print-a-hex-number-after-a-0x-prefix.patch
* drivers-misc-sgi-gru-grumainc-remove-bogus-0x-prefix-from-printk.patch
i-need-old-gcc.patch
* mm-remove-extra-newline-from-allocation-stall-warning.patch
* arm-arch-arm-include-asm-pageh-needs-personalityh.patch
* prctl-remove-one-shot-limitation-for-changing-exe-link.patch
* prctl-remove-one-shot-limitation-for-changing-exe-link-fix.patch
* kbuild-simpler-generation-of-assembly-constants.patch
* ocfs2-dlm-clean-up-useless-bug_on-default-case-in-dlm_finalize_reco_handler.patch
* block-restore-proc-partitions-to-not-display-non-partitionable-removable-devices.patch
* kernel-watchdog-use-nmi-registers-snapshot-in-hardlockup-handler.patch
mm.patch
* mm-memcontrol-use-special-workqueue-for-creating-per-memcg-caches.patch
* slub-move-synchronize_sched-out-of-slab_mutex-on-shrink.patch
* slub-avoid-false-postive-warning.patch
* dont-touch-single-threaded-ptes-which-are-on-the-right-node.patch
* dont-touch-single-threaded-ptes-which-are-on-the-right-node-v3.patch
* vmscan-set-correct-defer-count-for-shrinker.patch
* mm-compaction-allow-compaction-for-gfp_nofs-requests.patch
* mm-compaction-allow-compaction-for-gfp_nofs-requests-fix.patch
* mm-gup-make-unnecessarily-global-vma_permits_fault-static.patch
* mm-hugetlb-use-the-right-pte-val-for-compare-in-hugetlb_cow.patch
* mm-hugetlb-use-huge_pte_lock-instead-of-opencoding-the-lock.patch
* z3fold-limit-first_num-to-the-actual-range-of-possible-buddy-indexes.patch
* kmemleak-fix-reference-to-documentation.patch
* mm-vmalloc-replace-opencoded-4-level-page-walkers.patch
* mm-dont-steal-highatomic-pageblock.patch
* mm-prevent-double-decrease-of-nr_reserved_highatomic.patch
* mm-try-to-exhaust-highatomic-reserve-before-the-oom.patch
* mm-make-unreserve-highatomic-functions-reliable.patch
* mm-vmallocc-simplify-proc-vmallocinfo-implementation.patch
* mm-thp-avoid-unlikely-branches-for-split_huge_pmd.patch
* mm-mempolicy-clean-up-__gfp_thisnode-confusion-in-policy_zonelist.patch
* mm-mempolicy-clean-up-__gfp_thisnode-confusion-in-policy_zonelist-checkpatch-fixes.patch
* mm-compaction-fix-nr_isolated_-stats-for-pfn-based-migration.patch
* shmem-avoid-huge-pages-for-small-files.patch
* shmem-avoid-maybe-uninitialized-warning.patch
* mm-use-the-correct-page-size-when-removing-the-page.patch
* mm-update-mmu_gather-range-correctly.patch
* mm-hugetlb-add-tlb_remove_hugetlb_entry-for-handling-hugetlb-pages.patch
* mm-add-tlb_remove_check_page_size_change-to-track-page-size-change.patch
* mm-remove-the-page-size-change-check-in-tlb_remove_page.patch
* mm-fixup-get_user_pages-comments.patch
* mm-mempolicyc-forbid-static-or-relative-flags-for-local-numa-mode.patch
* mm-page_owner-align-with-pageblock_nr-pages.patch
* mm-walk-the-zone-in-pageblock_nr_pages-steps.patch
* kasan-support-panic_on_warn.patch
* mm-percpuc-fix-panic-triggered-by-bug_on-falsely.patch
* fs-proc-arrayc-slightly-improve-render_sigset_t.patch
* hung_task-decrement-sysctl_hung_task_warnings-only-if-it-is-positive.patch
* kernel-smp-define-pr_fmt-for-smpc.patch
* kernel-smp-make-the-smp-boot-message-common-on-all-arches.patch
* kernel-smp-tell-the-user-were-bringing-up-secondary-cpus.patch
* get_maintainer-look-for-arbitrary-letter-prefixes-in-sections.patch
* maintainers-add-b-for-uri-where-to-file-bugs.patch
* maintainers-add-drm-and-drm-i915-bug-filing-info.patch
* maintainers-add-c-for-uri-for-chat-where-developers-hang-out.patch
* maintainers-add-drm-and-drm-i915-irc-channels.patch
* let-config_strict_devmem-depends-on-config_devmem.patch
* lib-rbtreec-fix-typo-in-comment-of-____rb_erase_color.patch
* lib-add-crc64-ecma-module.patch
* checkpatch-dont-try-to-get-maintained-status-when-no-tree-is-given.patch
* scripts-checkpatchpl-fix-spelling.patch
* checkpatch-dont-check-pl-files-improve-absolute-path-commit-log-test.patch
* vfs-change-d_manage-to-take-a-struct-path.patch
* vfs-add-path_is_mountpoint-helper.patch
* vfs-add-path_has_submounts.patch
* autofs-change-autofs4_expire_wait-to-take-struct-path.patch
* autofs-change-autofs4_wait-to-take-struct-path.patch
* autofs-use-path_is_mountpoint-to-fix-unreliable-d_mountpoint-checks.patch
* autofs-use-path_has_submounts-to-fix-unreliable-have_submount-checks.patch
* vfs-remove-unused-have_submounts-function.patch
* signals-avoid-unnecessary-taking-of-sighand-siglock.patch
* kdump-vmcoreinfo-report-actual-value-of-phys_base.patch
* relay-check-array-offset-before-using-it.patch
* kconfig-lib-kconfigdebug-fix-references-to-documenation.patch
* kconfig-lib-kconfigubsan-fix-reference-to-ubsan-documentation.patch
* debug-more-properly-delay-for-secondary-cpus.patch
* debug-more-properly-delay-for-secondary-cpus-fix.patch
* initramfs-select-builtin-initram-compression-algorithm-on-kconfig-instead-of-makefile.patch
* initramfs-allow-again-choice-of-the-embedded-initram-compression-algorithm.patch
* ipc-semc-avoid-using-spin_unlock_wait.patch
* ipc-sem-add-hysteresis.patch
* ipc-msg-make-msgrcv-work-with-long_min.patch
* ipc-sem-do-not-call-wake_sem_queue_do-prematurely.patch
* ipc-sem-rework-task-wakeups.patch
* ipc-sem-rework-task-wakeups-checkpatch-fixes.patch
* ipc-sem-optimize-perform_atomic_semop.patch
* ipc-sem-optimize-perform_atomic_semop-checkpatch-fixes.patch
* ipc-sem-explicitly-inline-check_restart.patch
* ipc-sem-use-proper-list-api-for-pending_list-wakeups.patch
linux-next.patch
* drivers-net-wireless-intel-iwlwifi-dvm-calibc-fix-min-warning.patch
* kexec_file-allow-arch-specific-memory-walking-for-kexec_add_buffer.patch
* kexec_file-change-kexec_add_buffer-to-take-kexec_buf-as-argument.patch
* kexec_file-factor-out-kexec_locate_mem_hole-from-kexec_add_buffer.patch
* powerpc-change-places-using-config_kexec-to-use-config_kexec_core-instead.patch
* powerpc-factor-out-relocation-code-in-module_64c.patch
* powerpc-implement-kexec_file_load.patch
* powerpc-add-functions-to-read-elf-files-of-any-endianness.patch
* powerpc-add-support-for-loading-elf-kernels-with-kexec_file_load.patch
* powerpc-add-purgatory-for-kexec_file_load-implementation.patch
* powerpc-enable-config_kexec_file-in-powerpc-server-defconfigs.patch
* powerpc-ima-get-the-kexec-buffer-passed-by-the-previous-kernel.patch
* ima-on-soft-reboot-restore-the-measurement-list.patch
* ima-permit-duplicate-measurement-list-entries.patch
* ima-maintain-memory-size-needed-for-serializing-the-measurement-list.patch
* powerpc-ima-send-the-kexec-buffer-to-the-next-kernel.patch
* ima-on-soft-reboot-save-the-measurement-list.patch
* ima-store-the-builtin-custom-template-definitions-in-a-list.patch
* ima-support-restoring-multiple-template-formats.patch
* ima-define-a-canonical-binary_runtime_measurements-list-format.patch
* ima-platform-independent-hash-value.patch
mm-add-strictlimit-knob-v2.patch
make-sure-nobodys-leaking-resources.patch
releasing-resources-with-children.patch
make-frame_pointer-default=y.patch
kernel-forkc-export-kernel_thread-to-modules.patch
mutex-subsystem-synchro-test-module.patch
slab-leaks3-default-y.patch
add-debugging-aid-for-memory-initialisation-problems.patch
workaround-for-a-pci-restoring-bug.patch
^ permalink raw reply
* linux-next: Tree for Oct 28
From: Stephen Rothwell @ 2016-10-28 3:41 UTC (permalink / raw)
To: linux-next; +Cc: linux-kernel
Hi all,
There will probably be no linux-next releases next week while I attend
the Kernel Summit.
Changes since 20161027:
The akpm-current tree lost its build failures.
Non-merge commits (relative to Linus' tree): 3098
3842 files changed, 227213 insertions(+), 59787 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 245 trees (counting Linus' and 35 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 (e3300ffef065 Merge tag 'for-linus-4.9-rc2-ofs-1' of git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux)
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 (989cea5c14be kbuild: prevent lib-ksyms.o rebuilds)
Merging arc-current/for-curr (e2192b253de8 ARC: module: print pretty section names)
Merging arm-current/fixes (6127d124ee4e ARM: wire up new pkey syscalls)
Merging m68k-current/for-linus (6736e65effc3 m68k: Migrate exception table users off module.h and onto extable.h)
Merging metag-fixes/fixes (35d04077ad96 metag: Only define atomic_dec_if_positive conditionally)
Merging powerpc-fixes/fixes (fb479e44a9e2 powerpc/64s: relocation, register save fixes for system reset interrupt)
Merging sparc/master (a74ad5e660a9 sparc64: Handle extremely large kernel TLB range flushes more gracefully.)
Merging net/master (9ee7837449b3 net sched filters: fix notification of filter delete with proper handle)
CONFLICT (content): Merge conflict in drivers/net/ethernet/qlogic/Kconfig
Applying: qed*: merge fix for CONFIG_INFINIBAND_QEDR Kconfig move
Merging ipsec/master (7f92083eb58f vti6: flush x-netns xfrm cache when vti interface is removed)
Merging netfilter/master (7034b566a4e7 netfilter: fix nf_queue handling)
Merging ipvs/master (ea43f860d984 Merge branch 'ethoc-fixes')
Merging wireless-drivers/master (d3532ea6ce4e brcmfmac: avoid maybe-uninitialized warning in brcmf_cfg80211_start_ap)
Merging mac80211/master (b4f7f4ad425a mac80211: fix some sphinx warnings)
Merging sound-current/for-linus (bdc3478f90cd ALSA: usb-audio: Add quirk for Syntek STK1160)
Merging pci-current/for-linus (349d941e1ff1 PCI: qcom: Fix pp->dev usage before assignment)
Merging driver-core.current/driver-core-linus (248ff0216543 driver core: Make Kconfig text for DEBUG_TEST_DRIVER_REMOVE stronger)
Merging tty.current/tty-linus (009e39ae44f4 vt: clear selection before resizing)
Merging usb.current/usb-linus (c1aa67729a1d Merge tag 'usb-ci-v4.9-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb into usb-linus)
Merging usb-gadget-fixes/fixes (a1aa8cf6471b Revert "Documentation: devicetree: dwc2: Deprecate g-tx-fifo-size")
Merging usb-serial-fixes/usb-linus (07d9a380680d Linux 4.9-rc2)
Merging usb-chipidea-fixes/ci-for-usb-stable (991d5add50a5 usb: chipidea: host: fix NULL ptr dereference during shutdown)
Merging phy/fixes (1001354ca341 Linux 4.9-rc1)
Merging staging.current/staging-linus (e866dd8aab76 greybus: fix a leak on error in gb_module_create())
Merging char-misc.current/char-misc-linus (cfcc1456e4a2 Merge tag 'extcon-fixes-for-4.9-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon into char-misc-linus)
Merging input-current/for-linus (324ae0958cab Input: psmouse - cleanup Focaltech code)
Merging crypto-current/master (6d4952d9d9d4 hwrng: core - Don't use a stack buffer in add_early_randomness())
Merging ide/master (797cee982eef Merge branch 'stable-4.8' of git://git.infradead.org/users/pcmoore/audit)
Merging rr-fixes/fixes (8244062ef1e5 modules: fix longstanding /proc/kallsyms vs module insertion race.)
Merging vfio-fixes/for-linus (05692d7005a3 vfio/pci: Fix integer overflows, bitmask check)
Merging kselftest-fixes/fixes (29b4817d4018 Linux 4.8-rc1)
Merging backlight-fixes/for-backlight-fixes (68feaca0b13e backlight: pwm: Handle EPROBE_DEFER while requesting the PWM)
Merging ftrace-fixes/for-next-urgent (6224beb12e19 tracing: Have branch tracer use recursive field of task struct)
Merging mfd-fixes/for-mfd-fixes (51717929d835 mfd: intel_soc_pmic_bxtwc: Fix usbc interrupt)
Merging drm-intel-fixes/for-linux-next-fixes (07d9a380680d Linux 4.9-rc2)
Merging kbuild/for-next (fbcbee25745d Merge branches 'kbuild/kbuild' and 'kbuild/misc' into kbuild/for-next)
Merging asm-generic/master (de4be6b87b6b asm-generic: page.h: fix comment typo)
CONFLICT (content): Merge conflict in include/asm-generic/percpu.h
Merging arc/for-next (1001354ca341 Linux 4.9-rc1)
Merging arm/for-next (509d3b3effe2 Merge branches 'fixes', 'misc', 'sa1100-base' and 'syscalls' into for-next)
Merging arm-perf/for-next/perf (694d0d0bb203 Linux 4.8-rc2)
Merging arm-soc/for-next (83cb44244ff6 Merge branch 'fixes' into for-next)
Merging pinctrl/for-next (969cc0f87517 Merge branch 'devel' into for-next)
Merging amlogic/for-next (5a0803bd5ae2 ARM64: dts: meson-gxbb-odroidc2: Enable USB Nodes)
Merging at91/at91-next (0f59c948faed Merge tag 'at91-ab-4.8-defconfig' of git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux into at91-next)
Merging bcm2835/for-next (1443dff71db6 Merge branch anholt/bcm2835-dt-64-next into for-next)
Merging berlin/berlin/for-next (5153351425c9 Merge branch 'berlin/dt' into berlin/for-next)
Merging cortex-m/for-next (f719a0d6a854 ARM: efm32: switch to vendor,device compatible strings)
Merging imx-mxs/for-next (4020cd6682d6 Merge branch 'zte/dt64' into for-next)
Merging keystone/next (fb2a68db621a Merge branch 'for_4.9/keystone_dts' into next)
Merging mvebu/for-next (81f448072d1d Merge branch 'mvebu/dt64' into mvebu/for-next)
Merging omap/for-next (624018387bcf Merge branch 'omap-for-v4.9/dt-v2' into for-next)
Merging omap-pending/for-next (c20c8f750d9f ARM: OMAP2+: hwmod: fix _idle() hwmod state sanity check sequence)
Merging qcom/for-next (c49806e0fa1e Merge branch 'arm64-for-5.0' into all-for-5.0)
Merging renesas/next (b11b4e1d2653 Merge branches 'arm64-dt-for-v4.10', 'dt-for-v4.10', 'soc-for-v4.10' and 'arm64-defconfig-for-v4.10' into next)
Merging rockchip/for-next (8a3339648bb5 Merge branch 'v4.10-clk/next' into for-next)
Merging rpi/for-rpi-next (bc0195aad0da Linux 4.2-rc2)
Merging samsung/for-next (1a695a905c18 Linux 4.7-rc1)
Merging samsung-krzk/for-next (19350594a556 Merge branch 'next/dt' into for-next)
Merging tegra/for-next (74e8115883f5 Merge branch for-4.9/arm64/dt into for-next)
Merging arm64/for-next/core (db68f3e7594a arm64: tlbflush.h: add __tlbi() macro)
Merging blackfin/for-linus (391e74a51ea2 eth: bf609 eth clock: add pclk clock for stmmac driver probe)
CONFLICT (content): Merge conflict in arch/blackfin/mach-common/pm.c
Merging c6x/for-linux-next (ca3060d39ae7 c6x: Use generic clkdev.h header)
Merging cris/for-next (2dc024e94578 cris: return of class_create should be considered)
Merging h8300/h8300-next (58c57526711f h8300: Add missing include file to asm/io.h)
Merging hexagon/linux-next (02cc2ccfe771 Revert "Hexagon: fix signal.c compile error")
Merging ia64/next (fbb0e4da96f4 ia64: salinfo: use a waitqueue instead a sema down/up combo)
Merging m68k/for-next (6736e65effc3 m68k: Migrate exception table users off module.h and onto extable.h)
Merging m68knommu/for-next (baa6ae0f015b m68knommu: AMCORE board, add iMX i2c support)
Merging metag/for-next (f5d163aad31e metag: perf: fix build on Meta1)
Merging microblaze/next (52e9e6e05617 microblaze: pci: export isa_io_base to fix link errors)
Merging mips/mips-for-linux-next (1001354ca341 Linux 4.9-rc1)
Merging nios2/for-next (476080a79367 nios2: use of_property_read_bool)
Merging parisc-hd/for-next (c8d2bc9bc39e Linux 4.8)
Merging powerpc/next (08bf75ba852e powerpc/mm/hash64: Fix might_have_hea() check)
Merging fsl/next (e0b80f00bb96 arch/powerpc: Add CONFIG_FSL_DPAA to corenetXX_smp_defconfig)
Merging mpc5xxx/next (39e69f55f857 powerpc: Introduce the use of the managed version of kzalloc)
Merging s390/features (86651b6aa355 s390/cio: clean up DEV_STATE_SENSE_PGID)
Merging sparc-next/master (9f935675d41a Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input)
Merging sh/for-next (e61c10e468a4 sh: add device tree source for J2 FPGA on Mimas v2 board)
Merging tile/master (bf55d575234b tile: migrate exception table users off module.h and onto extable.h)
Merging uml/linux-next (dad223284407 um: Don't discard .text.exit section)
Merging unicore32/unicore32 (1ace5d1e3d4b unicore32-oldabi: add oldabi syscall interface)
Merging xtensa/xtensa-for-next (a4c6be5ad1d0 xtensa: disable MMU initialization option on MMUv2 cores)
Merging befs/for-next (3c8a965ad630 befs: remove signatures from comments)
Merging btrfs/next (8b8b08cbfb90 Btrfs: fix delalloc accounting after copy_from_user faults)
Merging btrfs-kdave/for-next (54626da80217 Merge branch 'for-next-next-4.9-20161024' into for-next-20161024)
Merging ceph/master (5130ccea7cf4 ceph: fix non static symbol warning)
Merging cifs/for-next (faad81c4f581 CIFS: iterate over posix acl xattr entry correctly in ACL_to_cifs_posix())
Merging configfs/for-next (42857cf512cb configfs: Return -EFBIG from configfs_write_bin_file.)
Merging ecryptfs/next (be280b25c328 ecryptfs: remove private bin2hex implementation)
Merging ext3/for_next (e952813e210b ext2: avoid bogus -Wmaybe-uninitialized warning)
Merging ext4/dev (d74f3d25289a ext4: add missing KERN_CONT to a few more debugging uses)
Merging f2fs/dev (f050cd028755 f2fs: use BIO_MAX_PAGES for bio allocation)
Merging freevxfs/for-next (bf1bb4b460c8 freevxfs: update Kconfig information)
Merging fscache/fscache (d52bd54db8be Merge branch 'akpm' (patches from Andrew))
Merging fuse/for-next (0ce267ff95a0 fuse: fix root dentry initialization)
Merging gfs2/for-next (a3443cda5588 Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security)
Merging jfs/jfs-next (240c5185c52d jfs: Simplify code)
Merging nfs/linux-next (14155cafeadd btrfs: assign error values to the correct bio structs)
Merging nfsd/nfsd-next (1136cf9890ab nfsd: more robust allocation failure handling in nfsd_reply_cache_init)
Merging orangefs/for-next (804b1737d712 orangefs: don't use d_time)
Merging overlayfs/overlayfs-next (204f6afd0743 ovl: split super.c)
Merging v9fs/for-next (a333e4bf2556 fs/9p: use fscache mutex rather than spinlock)
Merging ubifs/linux-next (c83ed4c9dbb3 ubifs: Abort readdir upon error)
Merging xfs/for-next (b77428b12b55 xfs: defer should abort intent items if the trans roll fails)
Merging file-locks/linux-next (07d9a380680d Linux 4.9-rc2)
Merging vfs/for-next (b26b5ef5ec7e Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs)
Merging vfs-jk/vfs (030b533c4fd4 fs: Avoid premature clearing of capabilities)
Merging vfs-miklos/next (c8d2bc9bc39e Linux 4.8)
Merging pci/next (1001354ca341 Linux 4.9-rc1)
Merging pstore/for-next/pstore (f88baf68ebe5 ramoops: move spin_lock_init after kmalloc error checking)
Merging hid/for-next (d7ff87349d20 Merge branches 'for-4.10/i2c-hid' and 'for-4.10/sony' into for-next)
Merging i2c/i2c/for-next (533169d164c6 i2c: imx: defer probe if bus recovery GPIOs are not ready)
Merging jdelvare-hwmon/master (08d27eb20666 Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs)
Merging dmi/master (c8d2bc9bc39e Linux 4.8)
Merging hwmon-staging/hwmon-next (c2d95c252f65 hwmon: (adm1275) Enable adm1278 VOUT sampling)
Merging jc_docs/docs-next (7a6992dc952e Merge branch 'doc-tweaks' into docs-next)
Merging v4l-dvb/master (778de0140232 Merge branch 'v4l_for_linus' into to_next)
Merging pm/linux-next (7d42a1e54d5e Merge branch 'acpica-fixes' into linux-next)
CONFLICT (content): Merge conflict in arch/arm/mach-imx/gpc.c
Merging idle/next (f55532a0c0b8 Linux 4.6-rc1)
Merging thermal/next (3105f234e0ab thermal/powerclamp: correct cpu support check)
Merging thermal-soc/next (c6935931c189 Linux 4.8-rc5)
Merging ieee1394/for-next (6449e31ddebd firewire: nosy: do not ignore errors in ioremap_nocache())
Merging dlm/next (aa9f1012858b dlm: don't specify WQ_UNBOUND for the ast callback workqueue)
Merging swiotlb/linux-next (386744425e35 swiotlb: Make linux/swiotlb.h standalone includible)
Merging net-next/master (002d8a1a6c11 net: skip genenerating uevents for network namespaces that are exiting)
CONFLICT (content): Merge conflict in net/core/dev.c
CONFLICT (content): Merge conflict in include/net/udp.h
CONFLICT (content): Merge conflict in include/linux/netdevice.h
CONFLICT (content): Merge conflict in drivers/net/ethernet/ibm/ibmvnic.c
Merging ipsec-next/master (2258d927a691 xfrm: remove unused helper)
Merging netfilter-next/master (84f5eedb983e netfilter: nf_tables: add fib expression)
Merging ipvs-next/master (ae9442f688c3 ipvs: Use IS_ERR_OR_NULL(svc) instead of IS_ERR(svc) || svc == NULL)
Merging wireless-drivers-next/master (3f8247c8c480 Merge tag 'iwlwifi-next-for-kalle-2016-10-25-2' of git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next)
Merging bluetooth/master (604907eeed85 Bluetooth: btwilink: Fix probe return value)
Merging mac80211-next/master (088e8df82f91 cfg80211: Add support to update connection parameters)
Merging rdma/for-next (2937f3757519 staging/lustre: Disable InfiniBand support)
Merging rdma-leon/rdma-next (1001354ca341 Linux 4.9-rc1)
Merging rdma-leon-test/testing/rdma-next (358a01eead9f Merge branch 'testing/queue-next' into testing/rdma-next)
Merging mtd/master (30656167bd23 MAINTAINERS: add more people to the MTD maintainer team)
Merging l2-mtd/master (30656167bd23 MAINTAINERS: add more people to the MTD maintainer team)
Merging nand/nand/next (98c3ac776a2b mtd: s3c2410: parse the device configuration from OF node)
Merging crypto/master (d7db7a882deb crypto: acomp - update testmgr with support for acomp)
Merging drm/drm-next (5481e27f6fd0 Merge tag 'drm-intel-next-2016-10-24' of git://anongit.freedesktop.org/drm-intel into drm-next)
Merging drm-panel/drm/panel/for-next (c96f566273bf drm/panel: Add JDI LT070ME05000 WUXGA DSI Panel)
Merging drm-intel/for-linux-next (1353ec383336 drm/i915: Correct pipe fault reporting string)
Merging drm-tegra/drm/tegra/for-next (08ee01789eeb drm/tegra: Fix window[0] base address corruption)
Merging drm-misc/topic/drm-misc (56df51d00320 drm/bridge: fix platform_no_drv_owner.cocci warnings)
CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/intel_dp.c
Merging drm-exynos/exynos-drm/for-next (7d1e04231461 Merge tag 'usercopy-v4.8-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux)
Merging drm-msm/msm-next (7a3bcc0a8e2a drm/msm: bump kernel api version for explicit fencing)
Merging hdlcd/for-upstream/hdlcd (523d939ef98f Linux 4.7)
Merging mali-dp/for-upstream/mali-dp (156f3a886cf0 drm/arm: mark symbols static where possible)
CONFLICT (content): Merge conflict in drivers/gpu/drm/arm/malidp_planes.c
Merging sunxi/sunxi/for-next (3896002338d5 Merge branches 'sunxi/clk-fixes-for-4.9', 'sunxi/clk-for-4.10', 'sunxi/defconfig-for-4.10', 'sunxi/drm-fixes-for-4.9', 'sunxi/drm-for-4.10', 'sunxi/dt-for-4.10' and 'sunxi/fixes-for-4.9' into sunxi/for-next)
Merging kspp/for-next/kspp (09dd109d8241 latent_entropy: Mark functions with __latent_entropy)
CONFLICT (add/add): Merge conflict in scripts/gcc-plugins/latent_entropy_plugin.c
Merging kconfig/for-next (5bcba792bb30 localmodconfig: Fix whitespace repeat count after "tristate")
Merging regmap/for-next (1001354ca341 Linux 4.9-rc1)
Merging sound/for-next (bdc3478f90cd ALSA: usb-audio: Add quirk for Syntek STK1160)
Merging sound-asoc/for-next (52ede60ca17f Merge remote-tracking branches 'asoc/topic/wm8580', 'asoc/topic/wm8753', 'asoc/topic/wm9705', 'asoc/topic/wm9712' and 'asoc/topic/wm9713' into asoc-next)
Merging modules/modules-next (a467a672cf09 MAINTAINERS: Begin module maintainer transition)
Merging input/next (8dd5e0b364e5 Input: da9063 - fix module autoload when registered via OF)
Merging block/for-next (5613beb8642f Merge branch 'for-4.10/block' into for-next)
Merging lightnvm/for-next (07d9a380680d Linux 4.9-rc2)
Merging device-mapper/for-next (5c5eb3db2893 dm cache metadata: DM_CACHE_FEATURE_INCOMPAT_SEP_DIRTY_BITS)
Merging pcmcia/master (e8e68fd86d22 pcmcia: do not break rsrc_nonstatic when handling anonymous cards)
Merging mmc/next (ed23c95a5414 Merge branch 'fixes' into next)
Merging kgdb/kgdb-next (7a6653fca500 kdb: Fix handling of kallsyms_symbol_next() return value)
Merging md/for-next (85deaf8862ed raid5: revert commit 11367799f3d1)
Merging mfd/for-mfd-next (77f298a18ff8 mfd: sun4i-gpadc: Fix 'cast from pointer to integer of different size' warning)
Merging backlight/for-backlight-next (0c9501f823a4 backlight: pwm_bl: Handle gpio that can sleep)
Merging battery/for-next (44fccac4ff17 power: supply: lp8788: remove an unneeded NULL check)
Merging omap_dss2/for-next (c456a2f30de5 video: smscufx: remove unused variable)
Merging regulator/for-next (1fcfba653094 Merge remote-tracking branches 'regulator/topic/arizona' and 'regulator/topic/tps6507x' into regulator-next)
Merging security/next (07d9a380680d Linux 4.9-rc2)
Merging integrity/next (56078b570983 module: Fully remove the kernel_module_from_file hook)
Merging keys/keys-next (ed51e44e914c Merge branch 'keys-asym-keyctl' into keys-next)
Merging selinux/next (1306d8e1c09f Merge tag 'tpmdd-next-20160927' of git://git.infradead.org/users/jjs/linux-tpmdd into ra-next)
Merging tpmdd/next (213ebc81ac3f tmp/tpm_crb: implement runtime pm for tpm_crb)
Merging watchdog/master (39487f6688a5 watchdog: imx2_wdt: add pretimeout function support)
Merging iommu/next (13a08259187c Merge branches 'x86/amd', 'x86/vt-d', 'arm/exynos', 'arm/mediatek', 'arm/renesas' and 'arm/smmu' into next)
Merging dwmw2-iommu/master (2566278551d3 Merge git://git.infradead.org/intel-iommu)
Merging vfio/next (61771468e0a5 vfio_pci: use pci_alloc_irq_vectors)
Merging trivial/for-next (380cc42d5a6c nvme: add missing \n to end of dev_warn message)
Merging audit/next (7ff89ac608d9 audit: add exclude filter extension to feature bitmap)
Merging devicetree/for-next (87e5fc99b028 DT: irqchip: renesas-irqc: document R8A7743/5 support)
Merging mailbox/mailbox-for-next (a649244de727 dt-bindings: mailbox: Add Amlogic Meson MHU Bindings)
Merging spi/for-next (dfbac252531d Merge remote-tracking branches 'spi/topic/imx', 'spi/topic/omap' and 'spi/topic/spidev' into spi-next)
Merging tip/auto-latest (d4721e29ba89 Merge branch 'x86/urgent')
Merging clockevents/clockevents/next (1d661bf5327a clocksource/drivers/time-armada-370-xp: Fix return value check)
Merging edac/linux_next (12f0721c5a70 sb_edac: correctly fetch DIMM width on Ivy Bridge and Haswell)
Merging edac-amd/for-next (90e493d7d51c EDAC, altera: Disable IRQs while injecting SDRAM errors)
Merging irqchip/irqchip/for-next (0ccb54a7dba0 Merge branch 'irqchip/core' into irqchip/for-next)
Merging ftrace/for-next (f971cc9aabc2 tracing: Have max_latency be defined for HWLAT_TRACER as well)
Merging rcu/rcu/next (367b548872c8 Documentation/RCU: Fix minor typo)
Merging kvm/linux-next (07d9a380680d Linux 4.9-rc2)
Merging kvm-arm/next (0099b7701f52 KVM: arm/arm64: vgic: Don't flush/sync without a working vgic)
Merging kvm-mips/next (07d9a380680d Linux 4.9-rc2)
Merging kvm-ppc/kvm-ppc-next (c63517c2e381 KVM: PPC: Book3S: correct width in XER handling)
Merging kvm-ppc-paulus/kvm-ppc-next (fa73c3b25bd8 KVM: PPC: Book3s PR: Allow access to unprivileged MMCR2 register)
Merging kvms390/next (b0eb91ae630a Merge remote-tracking branch 'kvms390/s390forkvm' into kvms390next)
Merging xen-tip/linux-next (a6a198bc60e6 xen/x86: Update topology map for PV VCPUs)
Merging percpu/for-next (3ca45a46f8af percpu: ensure the requested alignment is power of two)
Merging workqueues/for-next (8bc4a0445596 Merge branch 'for-4.9' into for-4.10)
Merging drivers-x86/for-next (304887041d95 platform/x86: Introduce support for Mellanox hotplug driver)
Merging chrome-platform/for-next (31b764171cb5 Revert "platform/chrome: chromeos_laptop: Add Leon Touch")
Merging hsi/for-next (7ac5d7b1a125 HSI: hsi_char.h: use __u32 from linux/types.h)
Merging leds/for-next (f04dfd0e937b leds: pca9532: Use default trigger value from platform data)
Merging ipmi/for-next (fc3357a8b71e ipmi: Update documentation)
Merging driver-core/driver-core-next (07d9a380680d Linux 4.9-rc2)
Merging tty/tty-next (07d9a380680d Linux 4.9-rc2)
Merging usb/usb-next (6110c425d98b usb: ohci-da8xx: Remove code that references mach)
Merging usb-gadget/next (1001354ca341 Linux 4.9-rc1)
Merging usb-serial/usb-next (a98b69002a16 USB: serial: ch341: add debug output for chip version)
Merging usb-chipidea-next/ci-for-usb-next (c6900310b6cc usb: chipidea: imx: Disable internal 60Mhz clock with ULPI PHY)
Merging phy-next/next (7809cd2ce6ab phy: meson: add USB2 PHY support for Meson8b and GXBB)
Merging staging/staging-next (54dc7ed37d39 Staging: media: davinci_vpfe: fix indentation issue in vpfe_video.c)
CONFLICT (content): Merge conflict in drivers/staging/wlan-ng/p80211netdev.c
CONFLICT (modify/delete): drivers/staging/iio/accel/sca3000_core.c deleted in staging/staging-next and modified in HEAD. Version HEAD of drivers/staging/iio/accel/sca3000_core.c left in tree.
CONFLICT (content): Merge conflict in Documentation/devicetree/bindings/i2c/trivial-devices.txt
$ git rm -f drivers/staging/iio/accel/sca3000_core.c
Merging char-misc/char-misc-next (07d9a380680d Linux 4.9-rc2)
Merging extcon/extcon-next (67fafcf82c3e extcon: usb-gpio: Add VBUS detection support)
Merging slave-dma/next (3277a5ccb332 Merge branch 'topic/st_fdma' into next)
Merging cgroup/for-next (4221d2ce6e57 Merge branch 'for-4.9' into for-next)
Merging scsi/for-next (16a142954a55 Merge branch 'misc' into for-next)
Merging target-updates/for-next (291e3e51a34d target: fix spelling mistake: "limitiation" -> "limitation")
Merging target-merge/for-next-merge (2994a7518317 cxgb4: update Kconfig and Makefile)
Merging libata/for-next (19f14deb00b3 Merge branch 'for-4.9-fixes' into for-next)
Merging binfmt_misc/for-next (4af75df6a410 binfmt_misc: add F option description to documentation)
Merging vhost/linux-next (789ffaecf80b virtio_pci: Limit DMA mask to 44 bits for legacy virtio devices)
Merging remoteproc/for-next (7a6271a80cae remoteproc/wkup_m3: Use MODULE_DEVICE_TABLE to export alias)
CONFLICT (content): Merge conflict in drivers/remoteproc/remoteproc_core.c
Merging rpmsg/for-next (20b1f39a51dc Merge branches 'hwspinlock-next', 'rpmsg-next' and 'rproc-next' into for-next)
Merging gpio/for-next (af223dd86d98 Merge branch 'devel' into for-next)
Merging dma-mapping/dma-mapping-next (1001354ca341 Linux 4.9-rc1)
Merging pwm/for-next (dc8e6e1e8f2d Merge branch 'for-4.9/drivers' into for-next)
Merging dma-buf/for-next (194cad44c4e1 dma-buf/sync_file: improve Kconfig description for Sync Files)
CONFLICT (content): Merge conflict in drivers/dma-buf/Kconfig
Merging userns/for-next (ce99dd5fd5f6 mm: Add a user_ns owner to mm_struct and fix ptrace_may_access)
Merging ktest/for-next (2dcd0af568b0 Linux 4.6)
Merging clk/clk-next (26f18452048e clk: imx: improve precision of AV PLL to 1 Hz)
Merging random/dev (59b8d4f1f5d2 random: use for_each_online_node() to iterate over NUMA nodes)
Merging aio/master (b562e44f507e Linux 4.5)
Merging kselftest/next (fecf861e765b selftests/futex: Check ANSI terminal color support)
Merging y2038/y2038 (549eb7b22e24 AFS: Correctly use 64-bit time for UUID)
CONFLICT (content): Merge conflict in fs/afs/main.c
Merging luto-misc/next (2dcd0af568b0 Linux 4.6)
Merging borntraeger/linux-next (dcc37f904443 processor.h: remove cpu_relax_lowlatency)
Merging livepatching/for-next (2992ef29ae01 livepatch/module: make TAINT_LIVEPATCH module-specific)
Merging coresight/next (96a7cd0a85a1 coresight: tmc: Remove duplicate memset)
Merging rtc/rtc-next (290cd0f07f0c rtc: cmos: don't refer to asm-generic/rtc.h)
Merging hwspinlock/for-next (bd5717a4632c hwspinlock: qcom: Correct msb in regmap_field)
Merging nvdimm/libnvdimm-for-next (52e73eb2872c device-dax: fix percpu_ref_exit ordering)
Merging dax-misc/dax-misc (4d9a2c874667 dax: Remove i_mmap_lock protection)
Merging akpm-current/current (61844692f80b ipc/sem: use proper list api for pending_list wakeups)
$ git checkout -b akpm remotes/origin/akpm/master
Applying: drivers/net/wireless/intel/iwlwifi/dvm/calib.c: simplfy min() expression
Applying: kexec_file: allow arch-specific memory walking for kexec_add_buffer
Applying: kexec_file: change kexec_add_buffer to take kexec_buf as argument
Applying: kexec_file: factor out kexec_locate_mem_hole from kexec_add_buffer
Applying: powerpc: change places using CONFIG_KEXEC to use CONFIG_KEXEC_CORE instead
Applying: powerpc: factor out relocation code in module_64.c
Applying: powerpc: implement kexec_file_load
Applying: powerpc: add functions to read ELF files of any endianness
Applying: powerpc: add support for loading ELF kernels with kexec_file_load
Applying: powerpc: add purgatory for kexec_file_load implementation
Applying: powerpc: enable CONFIG_KEXEC_FILE in powerpc server defconfigs
Applying: powerpc: ima: get the kexec buffer passed by the previous kernel
Applying: ima: on soft reboot, restore the measurement list
Applying: ima: permit duplicate measurement list entries
Applying: ima: maintain memory size needed for serializing the measurement list
Applying: powerpc: ima: send the kexec buffer to the next kernel
Applying: ima: on soft reboot, save the measurement list
Applying: ima: store the builtin/custom template definitions in a list
Applying: ima: support restoring multiple template formats
Applying: ima: define a canonical binary_runtime_measurements list format
Applying: ima: platform-independent hash value
Merging akpm/master (5a2a2c698010 ima: platform-independent hash value)
^ permalink raw reply
* next-20161028 build: 0 failures 1 warnings (next-20161028)
From: Build bot for Mark Brown @ 2016-10-28 9:01 UTC (permalink / raw)
To: kernel-build-reports, linaro-kernel, linux-next
Tree/Branch: next-20161028
Git describe: next-20161028
Commit: fee425e048 Add linux-next specific files for 20161028
Build Time: 167 min 49 sec
Passed: 10 / 10 (100.00 %)
Failed: 0 / 10 ( 0.00 %)
Errors: 0
Warnings: 1
Section Mismatches: 0
-------------------------------------------------------------------------------
defconfigs with issues (other than build errors):
1 warnings 0 mismatches : arm64-allmodconfig
-------------------------------------------------------------------------------
Warnings Summary: 1
1 ../include/linux/kernel.h:740:16: warning: comparison of distinct pointer types lacks a cast
===============================================================================
Detailed per-defconfig build reports below:
-------------------------------------------------------------------------------
arm64-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches
Warnings:
../include/linux/kernel.h:740:16: warning: comparison of distinct pointer types lacks a cast
-------------------------------------------------------------------------------
Passed with no errors, warnings or mismatches:
arm64-allnoconfig
arm-multi_v5_defconfig
arm-multi_v7_defconfig
x86_64-defconfig
arm-allmodconfig
arm-allnoconfig
x86_64-allnoconfig
arm-multi_v4t_defconfig
arm64-defconfig
^ permalink raw reply
* Re: linux-next: build warning in Linus' tree
From: Geert Uytterhoeven @ 2016-10-29 21:29 UTC (permalink / raw)
To: Linus Torvalds
Cc: Stephen Rothwell, Andrey Ryabinin, Alexander Potapenko,
Dmitry Vyukov, linux-next, Linux Kernel Mailing List
In-Reply-To: <CA+55aFwDL2_Ecuei4tYLH34RDmOba_COfr5JajasvYXA++yUgA@mail.gmail.com>
Hi Linus,
On Fri, Oct 28, 2016 at 1:01 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Thu, Oct 27, 2016 at 3:48 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>>
>> I wonder if we should make KASAN depend on !COMPILE_TEST, because it
>> does seem to disable a lot of build-time testing.
>
> Actually, we should probably just make the MEMORY_HOTPLUG dependency be
>
> depends on COMPILE_TEST || !KASAN
>
> since the memory-hotplug code should still *build* with KASAN, it just
> doesn't work. That's exactly what the COMPILE_TEST config option is
> there for - to get build coverage even for things that aren't
> necessarily sane to run.
In what way does it not work? Does it crash?
People do run COMPILE_TEST=y/allmodconfig kernels.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply
* Re: mmotm 2016-10-27-18-27 uploaded
From: Paul Gortmaker @ 2016-10-30 18:15 UTC (permalink / raw)
To: Andrew Morton
Cc: mm-commits, LKML, linux-mm, linux-fsdevel,
linux-next@vger.kernel.org, Stephen Rothwell, Michal Hocko,
broonie
In-Reply-To: <5812a9b6.OlAMBhewokz9/Mou%akpm@linux-foundation.org>
On Thu, Oct 27, 2016 at 9:28 PM, <akpm@linux-foundation.org> wrote:
> The mm-of-the-moment snapshot 2016-10-27-18-27 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
Just a heads up:
Somehow one of the akpm commits as it appears in linux-next has had
spaces replaced with garbage chars:
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/scripts/get_maintainer.pl?id=b67071653d3fc9f9b73aab3e7978f060728bf392
Paul.
--
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
>
> You will need quilt to apply these patches to the latest Linus release (4.x
> or 4.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> http://ozlabs.org/~akpm/mmotm/series
>
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.
>
> This tree is partially included in linux-next. To see which patches are
> included in linux-next, consult the `series' file. Only the patches
> within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> linux-next.
>
> A git tree which contains the memory management portion of this tree is
> maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> by Michal Hocko. It contains the patches which are between the
> "#NEXT_PATCHES_START mm" and "#NEXT_PATCHES_END" markers, from the series
> file, http://www.ozlabs.org/~akpm/mmotm/series.
>
>
> A full copy of the full kernel tree with the linux-next and mmotm patches
> already applied is available through git within an hour of the mmotm
> release. Individual mmotm releases are tagged. The master branch always
> points to the latest release, so it's constantly rebasing.
>
> http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/
>
[...]
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply
* Re: linux-next: build warning in Linus' tree
From: Andrey Ryabinin @ 2016-10-30 19:05 UTC (permalink / raw)
To: Geert Uytterhoeven, Linus Torvalds
Cc: Stephen Rothwell, Alexander Potapenko, Dmitry Vyukov, linux-next,
Linux Kernel Mailing List
In-Reply-To: <CAMuHMdVSqTkockvOBChTfGt9PJBZiEqDiUAAcCSas2x9t6mD_g@mail.gmail.com>
On 10/30/2016 12:29 AM, Geert Uytterhoeven wrote:
> Hi Linus,
>
> On Fri, Oct 28, 2016 at 1:01 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>> On Thu, Oct 27, 2016 at 3:48 PM, Linus Torvalds
>> <torvalds@linux-foundation.org> wrote:
>>>
>>> I wonder if we should make KASAN depend on !COMPILE_TEST, because it
>>> does seem to disable a lot of build-time testing.
>>
>> Actually, we should probably just make the MEMORY_HOTPLUG dependency be
>>
>> depends on COMPILE_TEST || !KASAN
>>
>> since the memory-hotplug code should still *build* with KASAN, it just
>> doesn't work. That's exactly what the COMPILE_TEST config option is
>> there for - to get build coverage even for things that aren't
>> necessarily sane to run.
>
> In what way does it not work? Does it crash?
It doesn't crash, it will fail to online hotpluged memory.
Originally, we didn't have build-time dependency at all.
It appeared quite recently in 1e185736d214("mm: disable CONFIG_MEMORY_HOTPLUG when KASAN is enabled")
> People do run COMPILE_TEST=y/allmodconfig kernels.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
^ permalink raw reply
* Re: linux-next: bad commit in the sunxi tree
From: Michael Ellerman @ 2016-10-31 2:59 UTC (permalink / raw)
To: Maxime Ripard, Stephen Rothwell; +Cc: linux-next, linux-kernel
In-Reply-To: <20161027204137.ef6kxlzyvftcdomn@lukather>
Maxime Ripard <maxime.ripard@free-electrons.com> writes:
> On Thu, Oct 27, 2016 at 10:42:25AM +1100, Stephen Rothwell wrote:
>> On Tue, 25 Oct 2016 11:44:09 +0200 Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
>> > On Tue, Oct 25, 2016 at 09:22:55AM +1100, Stephen Rothwell wrote:
>> > > In today's sunxi tree
>> > > (git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git#sunxi/for-next)
>> > > I noticed that commit
>> > >
>> > > 3861b711f8b5 ("ARM: sun5i: chip: add a node for the w1 gpio controller")
>> > >
>> > > has no Signed-off-by from its committer.
>> >
>> > Thanks, this has been fixed.
>> >
>> > Just out of curiosity, what command do you run to catch this?
>>
>> None :-) I look at the differences in each tree as I fetch it and
>> just happen to notice some of these sometimes. I should have a git
>> hook to check that there is a Signed-off-by for the author and
>> committer, but I would have to invest some time to figure out how :-)
>
> Ok, that's actually the real question I had in mind, if you had a hook
> I could use in order to avoid that kind of things in the future :)
I don't run a hook, but I have a separate script which does checks like
that. I've pulled out the Signed-off-by check into a script below, which
might work for you, or at least give you something to start from.
cheers
#!/bin/bash
function check_sob_by_committer
{
local commit=$1
git rev-parse --verify ${commit}^2 > /dev/null 2>&1
if [[ $? -eq 0 ]]; then
# It has at least 2 parents, ie. it's a merge
# We don't sign off merges, so we're done
return
fi
committer=$(git log -1 --format='%cn <%ce>' $commit)
git log -1 --format=%b $commit | grep "Signed-off-by: $committer" > /dev/null
if [[ $? -ne 0 ]]; then
echo " Not SOB committer '$committer'"
return 1
fi
return 0
}
check_sob_by_committer $1
exit $?
^ permalink raw reply
* Re: linux-next: bad commit in the sunxi tree
From: Stephen Rothwell @ 2016-10-31 14:57 UTC (permalink / raw)
To: Michael Ellerman; +Cc: Maxime Ripard, linux-next, linux-kernel
In-Reply-To: <8737jd2pg6.fsf@concordia.ellerman.id.au>
Hi Michael,
On Mon, 31 Oct 2016 13:59:53 +1100 Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> I don't run a hook, but I have a separate script which does checks like
> that. I've pulled out the Signed-off-by check into a script below, which
> might work for you, or at least give you something to start from.
Turns out that there is no hook that gets runa ta fetch time, so thanks
for this I will adapt this into my "fetch the trees" script.
--
Cheers,
Stephen Rothwell
^ permalink raw reply
* Re: mmotm 2016-10-27-18-27 uploaded
From: Valdis.Kletnieks @ 2016-10-31 20:37 UTC (permalink / raw)
To: Paul Gortmaker
Cc: Andrew Morton, mm-commits, LKML, linux-mm, linux-fsdevel,
linux-next@vger.kernel.org, Stephen Rothwell, Michal Hocko,
broonie
In-Reply-To: <CAP=VYLqNv8p_ojkcjeWCN-nMumDg296UkV1b460KDHAXOHZSEA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 637 bytes --]
On Sun, 30 Oct 2016 14:15:30 -0400, Paul Gortmaker said:
> On Thu, Oct 27, 2016 at 9:28 PM, <akpm@linux-foundation.org> wrote:
> > The mm-of-the-moment snapshot 2016-10-27-18-27 has been uploaded to
> >
> > http://www.ozlabs.org/~akpm/mmotm/
>
> Just a heads up:
>
> Somehow one of the akpm commits as it appears in linux-next has had
> spaces replaced with garbage chars:
>
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/scripts/get_maintainer.pl?id=b67071653d3fc9f9b73aab3e7978f060728bf392
How... special. They're 0xA0 non-breaking-space chars. Somebody's
editor was obviously in the wrong mode. :)
[-- Attachment #2: Type: application/pgp-signature, Size: 484 bytes --]
^ permalink raw reply
* Re: linux-next: manual merge of the mali-dp tree with the drm-misc tree
From: Liviu Dudau @ 2016-11-03 17:19 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Daniel Vetter, Intel Graphics, linux-kernel, DRI, linux-next
In-Reply-To: <20161025112044.1a866eaa@canb.auug.org.au>
On Tue, Oct 25, 2016 at 11:20:44AM +1100, Stephen Rothwell wrote:
> Hi Liviu,
Hi Stephen,
>
> Today's linux-next merge of the mali-dp tree got a conflict in:
>
> drivers/gpu/drm/arm/malidp_planes.c
>
> between commit:
>
> ea0e1ce20f73 ("drm/arm: Use per-plane rotation property")
>
> from the drm-misc tree and commit:
>
> 9ebb89762c30 ("drm: mali-dp: Refactor plane initialisation")
>
> from the mali-dp tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
Sorry for delay in answering, I was on holiday.
I have revamped the mali-dp tree and rebased it on the newer
version of drm-next (which includes the drm-misc change) and pushed the
updated patch in my tree.
Best regards,
Liviu
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc drivers/gpu/drm/arm/malidp_planes.c
> index abaca03b9d36,9020c0d8399c..000000000000
> --- a/drivers/gpu/drm/arm/malidp_planes.c
> +++ b/drivers/gpu/drm/arm/malidp_planes.c
> @@@ -254,23 -284,33 +284,30 @@@ int malidp_de_planes_init(struct drm_de
> if (ret < 0)
> goto cleanup;
>
> + drm_plane_helper_add(&plane->base,
> + &malidp_de_plane_helper_funcs);
> + plane->hwdev = malidp->dev;
> + plane->layer = &map->layers[i];
> +
> + /* Skip the features which the SMART layer doesn't have */
> + if (id == DE_SMART)
> + continue;
> +
> - if (!drm->mode_config.rotation_property) {
> + /* SMART layer can't be rotated */
> + if (id != DE_SMART) {
> unsigned long flags = DRM_ROTATE_0 |
> DRM_ROTATE_90 |
> DRM_ROTATE_180 |
> DRM_ROTATE_270 |
> DRM_REFLECT_X |
> DRM_REFLECT_Y;
> - drm->mode_config.rotation_property =
> - drm_mode_create_rotation_property(drm, flags);
> + drm_plane_create_rotation_property(&plane->base,
> + DRM_ROTATE_0,
> + flags);
> }
>
> - drm_plane_helper_add(&plane->base,
> - &malidp_de_plane_helper_funcs);
> - plane->hwdev = malidp->dev;
> - plane->layer = &map->layers[i];
> - if (drm->mode_config.rotation_property)
> - drm_object_attach_property(&plane->base.base,
> - drm->mode_config.rotation_property,
> - DRM_ROTATE_0);
> -
> + malidp_hw_write(malidp->dev, MALIDP_ALPHA_LUT,
> + plane->layer->base + MALIDP_LAYER_COMPOSE);
> }
>
> kfree(formats);
>
--
====================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(ツ)_/¯
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply
* Re: linux-next: manual merge of the mali-dp tree with the drm-misc tree
From: Stephen Rothwell @ 2016-11-04 5:38 UTC (permalink / raw)
To: Liviu Dudau; +Cc: Daniel Vetter, Intel Graphics, linux-kernel, DRI, linux-next
In-Reply-To: <20161103171958.GA17265@e106497-lin.cambridge.arm.com>
Hi Liviu,
On Thu, 3 Nov 2016 17:19:58 +0000 Liviu Dudau <Liviu.Dudau@arm.com> wrote:
>
> I have revamped the mali-dp tree and rebased it on the newer
> version of drm-next (which includes the drm-misc change) and pushed the
> updated patch in my tree.
Thanks for that. However, several of the commits in your tree now have
no Signed-off-by from you as the committer :-(
--
Cheers,
Stephen Rothwell
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply
* Re: linux-next: manual merge of the mali-dp tree with the drm-misc tree
From: Liviu Dudau @ 2016-11-04 15:48 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Daniel Vetter, Intel Graphics, linux-kernel, DRI, linux-next
In-Reply-To: <20161104163854.2c416e21@canb.auug.org.au>
On Fri, Nov 04, 2016 at 04:38:54PM +1100, Stephen Rothwell wrote:
> Hi Liviu,
>
> On Thu, 3 Nov 2016 17:19:58 +0000 Liviu Dudau <Liviu.Dudau@arm.com> wrote:
> >
> > I have revamped the mali-dp tree and rebased it on the newer
> > version of drm-next (which includes the drm-misc change) and pushed the
> > updated patch in my tree.
>
> Thanks for that. However, several of the commits in your tree now have
> no Signed-off-by from you as the committer :-(
Brian Starkey is a co-maintainer for the Mali DP tree, so his Signed-off-by
alone should be good. Baoyou's patch is in my tree to stop him repeatedly
send me the same patch over and over again :) But yes, I will add my
Signed-off-by for that one.
Many thanks,
Liviu
>
> --
> Cheers,
> Stephen Rothwell
--
====================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(ツ)_/¯
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply
* Re: linux-next: manual merge of the mali-dp tree with the drm-misc tree
From: Stephen Rothwell @ 2016-11-04 16:55 UTC (permalink / raw)
To: Liviu Dudau
Cc: Daniel Vetter, Intel Graphics, DRI, linux-next, linux-kernel,
Ville Syrjälä, Brian Starkey
In-Reply-To: <20161104154802.GC17265@e106497-lin.cambridge.arm.com>
Hi Liviu,
On Fri, 4 Nov 2016 15:48:02 +0000 Liviu Dudau <Liviu.Dudau@arm.com> wrote:
>
> Brian Starkey is a co-maintainer for the Mali DP tree, so his Signed-off-by
> alone should be good. Baoyou's patch is in my tree to stop him repeatedly
> send me the same patch over and over again :) But yes, I will add my
> Signed-off-by for that one.
Sorry, but this is not sufficient. Please read section 11 of
Documentation/SubmittingPatches (or
Documentation/process/submitting-patches.rst where it has been moved
recently). If you are in the path of a patch to Linus, you must add a
Signed-off-by line, and as the person who committed those patches to
the tree, you are in the path.
--
Cheers,
Stephen Rothwell
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox