* linux-next: Tree for Sep 27 @ 2022-09-27 20:10 broonie 2022-09-27 21:13 ` linux-next: Tree for Sep 27 (uml 64-bit or 32-bit: tinyconfig) Randy Dunlap 0 siblings, 1 reply; 7+ messages in thread From: broonie @ 2022-09-27 20:10 UTC (permalink / raw) To: Linux Next Mailing List; +Cc: Linux Kernel Mailing List Hi all, Changes since 20220923: The vfs tree gained a conflict with the ext3 tree. The bluetooth tree gained conflict with the net tree. The various DRM trees gained even more conflicts with each other. The drivers-misc tree gained a conflict against the jc_docs tree. The drivers-misc tree gained a conflict against the drm tree. The v4l tree gained a conflict with the v4l-dvb-fixes tree. The net-next tree gained a conflict against the i2c tree. The kspp tree gained a conflict against the arm64 tree. The kspp tree gained a conflict against the arm64-fixes tree. The kspp tree gained a conflict against the bpf-next tree. The mm-stable tree gained a conflict against the bitmap tree. Non-merge commits (relative to Linus' tree): 9849 10393 files changed, 558039 insertions(+), 213574 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, arm64, 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 362 trees (counting Linus' and 100 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. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: linux-next: Tree for Sep 27 (uml 64-bit or 32-bit: tinyconfig) 2022-09-27 20:10 linux-next: Tree for Sep 27 broonie @ 2022-09-27 21:13 ` Randy Dunlap 2022-09-27 21:28 ` Paul E. McKenney 0 siblings, 1 reply; 7+ messages in thread From: Randy Dunlap @ 2022-09-27 21:13 UTC (permalink / raw) To: broonie, Linux Next Mailing List Cc: Linux Kernel Mailing List, Paul E. McKenney, linux-um On 9/27/22 13:10, broonie@kernel.org wrote: > Hi all, > > Changes since 20220923: > In file included from ../include/linux/notifier.h:16, from ../include/linux/memory_hotplug.h:7, from ../include/linux/mmzone.h:1244, from ../include/linux/gfp.h:7, from ../include/linux/slab.h:15, from ../include/linux/crypto.h:20, from ../arch/x86/um/shared/sysdep/kernel-offsets.h:5, from ../arch/um/kernel/asm-offsets.c:1: ../include/linux/srcu.h: In function ‘srcu_read_lock_nmisafe’: ../include/linux/srcu.h:181:26: error: implicit declaration of function ‘__srcu_read_lock_nmisafe’; did you mean ‘srcu_read_lock_nmisafe’? [-Werror=implicit-function-declaration] 181 | retval = __srcu_read_lock_nmisafe(ssp, true); | ^~~~~~~~~~~~~~~~~~~~~~~~ | srcu_read_lock_nmisafe ../include/linux/srcu.h: In function ‘srcu_read_unlock_nmisafe’: ../include/linux/srcu.h:226:17: error: implicit declaration of function ‘__srcu_read_unlock_nmisafe’; did you mean ‘srcu_read_unlock_nmisafe’? [-Werror=implicit-function-declaration] 226 | __srcu_read_unlock_nmisafe(ssp, idx, true); | ^~~~~~~~~~~~~~~~~~~~~~~~~~ | srcu_read_unlock_nmisafe -- ~Randy ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: linux-next: Tree for Sep 27 (uml 64-bit or 32-bit: tinyconfig) 2022-09-27 21:13 ` linux-next: Tree for Sep 27 (uml 64-bit or 32-bit: tinyconfig) Randy Dunlap @ 2022-09-27 21:28 ` Paul E. McKenney 2022-09-27 21:33 ` Randy Dunlap 0 siblings, 1 reply; 7+ messages in thread From: Paul E. McKenney @ 2022-09-27 21:28 UTC (permalink / raw) To: Randy Dunlap Cc: broonie, Linux Next Mailing List, Linux Kernel Mailing List, linux-um On Tue, Sep 27, 2022 at 02:13:29PM -0700, Randy Dunlap wrote: > > > On 9/27/22 13:10, broonie@kernel.org wrote: > > Hi all, > > > > Changes since 20220923: > > > > In file included from ../include/linux/notifier.h:16, > from ../include/linux/memory_hotplug.h:7, > from ../include/linux/mmzone.h:1244, > from ../include/linux/gfp.h:7, > from ../include/linux/slab.h:15, > from ../include/linux/crypto.h:20, > from ../arch/x86/um/shared/sysdep/kernel-offsets.h:5, > from ../arch/um/kernel/asm-offsets.c:1: > ../include/linux/srcu.h: In function ‘srcu_read_lock_nmisafe’: > ../include/linux/srcu.h:181:26: error: implicit declaration of function ‘__srcu_read_lock_nmisafe’; did you mean ‘srcu_read_lock_nmisafe’? [-Werror=implicit-function-declaration] > 181 | retval = __srcu_read_lock_nmisafe(ssp, true); > | ^~~~~~~~~~~~~~~~~~~~~~~~ > | srcu_read_lock_nmisafe > ../include/linux/srcu.h: In function ‘srcu_read_unlock_nmisafe’: > ../include/linux/srcu.h:226:17: error: implicit declaration of function ‘__srcu_read_unlock_nmisafe’; did you mean ‘srcu_read_unlock_nmisafe’? [-Werror=implicit-function-declaration] > 226 | __srcu_read_unlock_nmisafe(ssp, idx, true); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~ > | srcu_read_unlock_nmisafe Could you please send your .config or tell me how you generated it? Thanx, Paul ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: linux-next: Tree for Sep 27 (uml 64-bit or 32-bit: tinyconfig) 2022-09-27 21:28 ` Paul E. McKenney @ 2022-09-27 21:33 ` Randy Dunlap 2022-09-27 22:42 ` Paul E. McKenney 0 siblings, 1 reply; 7+ messages in thread From: Randy Dunlap @ 2022-09-27 21:33 UTC (permalink / raw) To: paulmck Cc: broonie, Linux Next Mailing List, Linux Kernel Mailing List, linux-um On 9/27/22 14:28, Paul E. McKenney wrote: > On Tue, Sep 27, 2022 at 02:13:29PM -0700, Randy Dunlap wrote: >> >> >> On 9/27/22 13:10, broonie@kernel.org wrote: >>> Hi all, >>> >>> Changes since 20220923: >>> >> >> In file included from ../include/linux/notifier.h:16, >> from ../include/linux/memory_hotplug.h:7, >> from ../include/linux/mmzone.h:1244, >> from ../include/linux/gfp.h:7, >> from ../include/linux/slab.h:15, >> from ../include/linux/crypto.h:20, >> from ../arch/x86/um/shared/sysdep/kernel-offsets.h:5, >> from ../arch/um/kernel/asm-offsets.c:1: >> ../include/linux/srcu.h: In function ‘srcu_read_lock_nmisafe’: >> ../include/linux/srcu.h:181:26: error: implicit declaration of function ‘__srcu_read_lock_nmisafe’; did you mean ‘srcu_read_lock_nmisafe’? [-Werror=implicit-function-declaration] >> 181 | retval = __srcu_read_lock_nmisafe(ssp, true); >> | ^~~~~~~~~~~~~~~~~~~~~~~~ >> | srcu_read_lock_nmisafe >> ../include/linux/srcu.h: In function ‘srcu_read_unlock_nmisafe’: >> ../include/linux/srcu.h:226:17: error: implicit declaration of function ‘__srcu_read_unlock_nmisafe’; did you mean ‘srcu_read_unlock_nmisafe’? [-Werror=implicit-function-declaration] >> 226 | __srcu_read_unlock_nmisafe(ssp, idx, true); >> | ^~~~~~~~~~~~~~~~~~~~~~~~~~ >> | srcu_read_unlock_nmisafe > > Could you please send your .config or tell me how you generated it? For x86_64 SUBARCH, ARCH=um: mkdir UML64 make ARCH=um SUBARCH=x86_64 O=UML64 tinyconfig make ARCH=um SUBARCH=x86_64 O=UML64 all -- ~Randy ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: linux-next: Tree for Sep 27 (uml 64-bit or 32-bit: tinyconfig) 2022-09-27 21:33 ` Randy Dunlap @ 2022-09-27 22:42 ` Paul E. McKenney 2022-09-28 3:27 ` Randy Dunlap 0 siblings, 1 reply; 7+ messages in thread From: Paul E. McKenney @ 2022-09-27 22:42 UTC (permalink / raw) To: Randy Dunlap Cc: broonie, Linux Next Mailing List, Linux Kernel Mailing List, linux-um On Tue, Sep 27, 2022 at 02:33:19PM -0700, Randy Dunlap wrote: > > > On 9/27/22 14:28, Paul E. McKenney wrote: > > On Tue, Sep 27, 2022 at 02:13:29PM -0700, Randy Dunlap wrote: > >> > >> > >> On 9/27/22 13:10, broonie@kernel.org wrote: > >>> Hi all, > >>> > >>> Changes since 20220923: > >>> > >> > >> In file included from ../include/linux/notifier.h:16, > >> from ../include/linux/memory_hotplug.h:7, > >> from ../include/linux/mmzone.h:1244, > >> from ../include/linux/gfp.h:7, > >> from ../include/linux/slab.h:15, > >> from ../include/linux/crypto.h:20, > >> from ../arch/x86/um/shared/sysdep/kernel-offsets.h:5, > >> from ../arch/um/kernel/asm-offsets.c:1: > >> ../include/linux/srcu.h: In function ‘srcu_read_lock_nmisafe’: > >> ../include/linux/srcu.h:181:26: error: implicit declaration of function ‘__srcu_read_lock_nmisafe’; did you mean ‘srcu_read_lock_nmisafe’? [-Werror=implicit-function-declaration] > >> 181 | retval = __srcu_read_lock_nmisafe(ssp, true); > >> | ^~~~~~~~~~~~~~~~~~~~~~~~ > >> | srcu_read_lock_nmisafe > >> ../include/linux/srcu.h: In function ‘srcu_read_unlock_nmisafe’: > >> ../include/linux/srcu.h:226:17: error: implicit declaration of function ‘__srcu_read_unlock_nmisafe’; did you mean ‘srcu_read_unlock_nmisafe’? [-Werror=implicit-function-declaration] > >> 226 | __srcu_read_unlock_nmisafe(ssp, idx, true); > >> | ^~~~~~~~~~~~~~~~~~~~~~~~~~ > >> | srcu_read_unlock_nmisafe > > > > Could you please send your .config or tell me how you generated it? > > > For x86_64 SUBARCH, ARCH=um: > > mkdir UML64 > make ARCH=um SUBARCH=x86_64 O=UML64 tinyconfig > make ARCH=um SUBARCH=x86_64 O=UML64 all Thank you! The diff shown below clears it up for me. Does it cover it for you as well? Thanx, Paul ------------------------------------------------------------------------ diff --git a/include/linux/srcu.h b/include/linux/srcu.h index 274d7200ce4e..565f60d57484 100644 --- a/include/linux/srcu.h +++ b/include/linux/srcu.h @@ -52,6 +52,8 @@ int init_srcu_struct(struct srcu_struct *ssp); #else /* Dummy definition for things like notifiers. Actual use gets link error. */ struct srcu_struct { }; +int __srcu_read_lock_nmisafe(struct srcu_struct *ssp, bool chknmisafe) __acquires(ssp); +void __srcu_read_unlock_nmisafe(struct srcu_struct *ssp, int idx, bool chknmisafe) __releases(ssp); #endif void call_srcu(struct srcu_struct *ssp, struct rcu_head *head, ^ permalink raw reply related [flat|nested] 7+ messages in thread
* Re: linux-next: Tree for Sep 27 (uml 64-bit or 32-bit: tinyconfig) 2022-09-27 22:42 ` Paul E. McKenney @ 2022-09-28 3:27 ` Randy Dunlap 2022-09-28 6:25 ` Paul E. McKenney 0 siblings, 1 reply; 7+ messages in thread From: Randy Dunlap @ 2022-09-28 3:27 UTC (permalink / raw) To: paulmck Cc: broonie, Linux Next Mailing List, Linux Kernel Mailing List, linux-um Hi Paul, On 9/27/22 15:42, Paul E. McKenney wrote: > On Tue, Sep 27, 2022 at 02:33:19PM -0700, Randy Dunlap wrote: >> >> >> On 9/27/22 14:28, Paul E. McKenney wrote: >>> On Tue, Sep 27, 2022 at 02:13:29PM -0700, Randy Dunlap wrote: >>>> >>>> >>>> On 9/27/22 13:10, broonie@kernel.org wrote: >>>>> Hi all, >>>>> >>>>> Changes since 20220923: >>>>> >>>> >>>> In file included from ../include/linux/notifier.h:16, >>>> from ../include/linux/memory_hotplug.h:7, >>>> from ../include/linux/mmzone.h:1244, >>>> from ../include/linux/gfp.h:7, >>>> from ../include/linux/slab.h:15, >>>> from ../include/linux/crypto.h:20, >>>> from ../arch/x86/um/shared/sysdep/kernel-offsets.h:5, >>>> from ../arch/um/kernel/asm-offsets.c:1: >>>> ../include/linux/srcu.h: In function ‘srcu_read_lock_nmisafe’: >>>> ../include/linux/srcu.h:181:26: error: implicit declaration of function ‘__srcu_read_lock_nmisafe’; did you mean ‘srcu_read_lock_nmisafe’? [-Werror=implicit-function-declaration] >>>> 181 | retval = __srcu_read_lock_nmisafe(ssp, true); >>>> | ^~~~~~~~~~~~~~~~~~~~~~~~ >>>> | srcu_read_lock_nmisafe >>>> ../include/linux/srcu.h: In function ‘srcu_read_unlock_nmisafe’: >>>> ../include/linux/srcu.h:226:17: error: implicit declaration of function ‘__srcu_read_unlock_nmisafe’; did you mean ‘srcu_read_unlock_nmisafe’? [-Werror=implicit-function-declaration] >>>> 226 | __srcu_read_unlock_nmisafe(ssp, idx, true); >>>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~ >>>> | srcu_read_unlock_nmisafe >>> >>> Could you please send your .config or tell me how you generated it? >> >> >> For x86_64 SUBARCH, ARCH=um: >> >> mkdir UML64 >> make ARCH=um SUBARCH=x86_64 O=UML64 tinyconfig >> make ARCH=um SUBARCH=x86_64 O=UML64 all > > Thank you! The diff shown below clears it up for me. Does it cover it > for you as well? Works for me. Thanks. Acked-by: Randy Dunlap <rdunlap@infradead.org> # build-tested > ------------------------------------------------------------------------ > > diff --git a/include/linux/srcu.h b/include/linux/srcu.h > index 274d7200ce4e..565f60d57484 100644 > --- a/include/linux/srcu.h > +++ b/include/linux/srcu.h > @@ -52,6 +52,8 @@ int init_srcu_struct(struct srcu_struct *ssp); > #else > /* Dummy definition for things like notifiers. Actual use gets link error. */ > struct srcu_struct { }; > +int __srcu_read_lock_nmisafe(struct srcu_struct *ssp, bool chknmisafe) __acquires(ssp); > +void __srcu_read_unlock_nmisafe(struct srcu_struct *ssp, int idx, bool chknmisafe) __releases(ssp); > #endif > > void call_srcu(struct srcu_struct *ssp, struct rcu_head *head, -- ~Randy ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: linux-next: Tree for Sep 27 (uml 64-bit or 32-bit: tinyconfig) 2022-09-28 3:27 ` Randy Dunlap @ 2022-09-28 6:25 ` Paul E. McKenney 0 siblings, 0 replies; 7+ messages in thread From: Paul E. McKenney @ 2022-09-28 6:25 UTC (permalink / raw) To: Randy Dunlap Cc: broonie, Linux Next Mailing List, Linux Kernel Mailing List, linux-um On Tue, Sep 27, 2022 at 08:27:13PM -0700, Randy Dunlap wrote: > Hi Paul, > > On 9/27/22 15:42, Paul E. McKenney wrote: > > On Tue, Sep 27, 2022 at 02:33:19PM -0700, Randy Dunlap wrote: > >> > >> > >> On 9/27/22 14:28, Paul E. McKenney wrote: > >>> On Tue, Sep 27, 2022 at 02:13:29PM -0700, Randy Dunlap wrote: > >>>> > >>>> > >>>> On 9/27/22 13:10, broonie@kernel.org wrote: > >>>>> Hi all, > >>>>> > >>>>> Changes since 20220923: > >>>>> > >>>> > >>>> In file included from ../include/linux/notifier.h:16, > >>>> from ../include/linux/memory_hotplug.h:7, > >>>> from ../include/linux/mmzone.h:1244, > >>>> from ../include/linux/gfp.h:7, > >>>> from ../include/linux/slab.h:15, > >>>> from ../include/linux/crypto.h:20, > >>>> from ../arch/x86/um/shared/sysdep/kernel-offsets.h:5, > >>>> from ../arch/um/kernel/asm-offsets.c:1: > >>>> ../include/linux/srcu.h: In function ‘srcu_read_lock_nmisafe’: > >>>> ../include/linux/srcu.h:181:26: error: implicit declaration of function ‘__srcu_read_lock_nmisafe’; did you mean ‘srcu_read_lock_nmisafe’? [-Werror=implicit-function-declaration] > >>>> 181 | retval = __srcu_read_lock_nmisafe(ssp, true); > >>>> | ^~~~~~~~~~~~~~~~~~~~~~~~ > >>>> | srcu_read_lock_nmisafe > >>>> ../include/linux/srcu.h: In function ‘srcu_read_unlock_nmisafe’: > >>>> ../include/linux/srcu.h:226:17: error: implicit declaration of function ‘__srcu_read_unlock_nmisafe’; did you mean ‘srcu_read_unlock_nmisafe’? [-Werror=implicit-function-declaration] > >>>> 226 | __srcu_read_unlock_nmisafe(ssp, idx, true); > >>>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~ > >>>> | srcu_read_unlock_nmisafe > >>> > >>> Could you please send your .config or tell me how you generated it? > >> > >> > >> For x86_64 SUBARCH, ARCH=um: > >> > >> mkdir UML64 > >> make ARCH=um SUBARCH=x86_64 O=UML64 tinyconfig > >> make ARCH=um SUBARCH=x86_64 O=UML64 all > > > > Thank you! The diff shown below clears it up for me. Does it cover it > > for you as well? > > Works for me. Thanks. > Acked-by: Randy Dunlap <rdunlap@infradead.org> # build-tested Thank you, Randy! Thanx, Paul > > ------------------------------------------------------------------------ > > > > diff --git a/include/linux/srcu.h b/include/linux/srcu.h > > index 274d7200ce4e..565f60d57484 100644 > > --- a/include/linux/srcu.h > > +++ b/include/linux/srcu.h > > @@ -52,6 +52,8 @@ int init_srcu_struct(struct srcu_struct *ssp); > > #else > > /* Dummy definition for things like notifiers. Actual use gets link error. */ > > struct srcu_struct { }; > > +int __srcu_read_lock_nmisafe(struct srcu_struct *ssp, bool chknmisafe) __acquires(ssp); > > +void __srcu_read_unlock_nmisafe(struct srcu_struct *ssp, int idx, bool chknmisafe) __releases(ssp); > > #endif > > > > void call_srcu(struct srcu_struct *ssp, struct rcu_head *head, > > -- > ~Randy ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2022-09-28 6:25 UTC | newest] Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2022-09-27 20:10 linux-next: Tree for Sep 27 broonie 2022-09-27 21:13 ` linux-next: Tree for Sep 27 (uml 64-bit or 32-bit: tinyconfig) Randy Dunlap 2022-09-27 21:28 ` Paul E. McKenney 2022-09-27 21:33 ` Randy Dunlap 2022-09-27 22:42 ` Paul E. McKenney 2022-09-28 3:27 ` Randy Dunlap 2022-09-28 6:25 ` Paul E. McKenney
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).