Hi all,
Changes since 20220728:
The hid tree gained a build failure which I fixed up.
The thermal tree gained a build failure, I used the version from 20220728
instead.
The net-next tree gained a conflict against the net tree.
The kvm tree gained a conflict with the kvms390-fixes tree.
The pinctrl tree gained a build failure for which I reverted a commit.
Non-merge commits (relative to Linus' tree): 12734
12594 files changed, 1319236 insertions(+), 278745 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 an arm64 defconfig, an allmodconfig build for x86_64, a
multi_v7_defconfig for arm and a native (arm64) build of tools/perf.
Below is a summary of the state of the merge.
I am currently merging 357 trees (counting Linus' and 98 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.
On 8/3/22 08:03, [email protected] wrote:
> Hi all,
>
> Changes since 20220728:
>
> The hid tree gained a build failure which I fixed up.
>
> The thermal tree gained a build failure, I used the version from 20220728
> instead.
>
> The net-next tree gained a conflict against the net tree.
>
> The kvm tree gained a conflict with the kvms390-fixes tree.
>
> The pinctrl tree gained a build failure for which I reverted a commit.
>
> Non-merge commits (relative to Linus' tree): 12734
> 12594 files changed, 1319236 insertions(+), 278745 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 an arm64 defconfig, an allmodconfig build for x86_64, a
> multi_v7_defconfig for arm and a native (arm64) build of tools/perf.
>
Hi broonie,
Thanks for keeping linux-next up while Stephen is on vacation.
What is missing here is powerpc build (ppc64_defconfig), since the
architecture is often used for cross-compile test.
And I think since we're at merge window for 6.0, we need to say
"Please do not add material for 6.1 until 6.0-rc1 have been
released".
Thanks.
--
An old man doll... just what I always wanted! - Clara
On Wed, Aug 03, 2022 at 08:48:58AM +0700, Bagas Sanjaya wrote:
> What is missing here is powerpc build (ppc64_defconfig), since the
> architecture is often used for cross-compile test.
No, it's not missing. Stephen's native PowerPC build has been
deliberately replaced with a native arm64 defconfig build since that's
the system I have access to and that's who's paying the bills here.
> And I think since we're at merge window for 6.0, we need to say
> "Please do not add material for 6.1 until 6.0-rc1 have been
> released".
Right, I didn't add a note about that. Hopefully people are sensible
enough to figure it out without the explicit statement in the -next
mails.