Hi all,
Changes since 20220920:
The net-next tree gained conflicts against Linus' tree and the net tree.
The nand tree gained a build failure so I used the version from
next-20220920.
The sound-asoc tree gained semantic conflicts against the i2c tree.
The tty tree gained a conflict against the usb-serial tree.
The soundwire tree gained a conflict against Linus' tree.
The bitmap tree lost its build failure.
Non-merge commits (relative to Linus' tree): 7972
9000 files changed, 445932 insertions(+), 192298 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 360 trees (counting Linus' and 99 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
Hi all,
On Wed, 21 Sep 2022 18:57:40 +1000 Stephen Rothwell <[email protected]> wrote:
>
> Changes since 20220920:
I forgot to mention that there will be no linux-next release tomorrow
(while all Aussies remember their Queen) or next week.
--
Cheers,
Stephen Rothwell
On Wed, Sep 21, 2022 at 11:13:04PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> On Wed, 21 Sep 2022 18:57:40 +1000 Stephen Rothwell <[email protected]> wrote:
> >
> > Changes since 20220920:
>
> I forgot to mention that there will be no linux-next release tomorrow
> (while all Aussies remember their Queen) or next week.
I'll not be able to pick this up tomorrow but I should be able to
provide some cover for next week.
Hi Mark,
On Wed, 21 Sep 2022 16:37:59 +0100 Mark Brown <[email protected]> wrote:
>
> On Wed, Sep 21, 2022 at 11:13:04PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > On Wed, 21 Sep 2022 18:57:40 +1000 Stephen Rothwell <[email protected]> wrote:
> > >
> > > Changes since 20220920:
> >
> > I forgot to mention that there will be no linux-next release tomorrow
> > (while all Aussies remember their Queen) or next week.
>
> I'll not be able to pick this up tomorrow but I should be able to
> provide some cover for next week.
Today should be fine (I skip a day or two every now and then anyway and
I will do Friday). Thanks for considering next week. I think just one
or two should be OK. I may even have time to do a couple myself (this
is not a holiday so much (helping my daughter move)).
It is a pain that it is at this end of the cycle again, sorry.
--
Cheers,
Stephen Rothwell