linux-next: Tree for Dec 14

linux-next: Tree for Dec 14

[broonie]

Hi all,

News: Releases may or may not happen over the next few days since I'm
getting a vacciene dose tomorrow.

Changes since 20211213:

The drm-intel tree gained a conflict with the drm-intel-fixes tree.

The dmaengine tree gained a conflict with the dmaengine-fixes tree.

Non-merge commits (relative to Linus' tree): 6251
 6873 files changed, 291130 insertions(+), 138903 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 defconfig for arm64, 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, arm64 allnoconfig, arm64 allyesconfig and i386,
and arm64 and htmldocs.

Below is a summary of the state of the merge.

I am currently merging 346 trees (counting Linus' and 94 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.

Re: linux-next: Tree for Dec 14

[Nathan Chancellor]

Hi Mark,

On Tue, Dec 14, 2021 at 10:32:22PM +0000, broonie@kernel.org wrote:
> Hi all,
> 
> News: Releases may or may not happen over the next few days since I'm
> getting a vacciene dose tomorrow.
> 
> Changes since 20211213:
> 
> The drm-intel tree gained a conflict with the drm-intel-fixes tree.
> 
> The dmaengine tree gained a conflict with the dmaengine-fixes tree.
> 
> Non-merge commits (relative to Linus' tree): 6251
>  6873 files changed, 291130 insertions(+), 138903 deletions(-)

Was there a conflict in mm/migrate.c with this release? It looks like
the ptl assignment was dropped in commit fd93c9fe58cc ("Merge branch
'akpm-current/current'") but I do not see that in any of the individual
mm/migrate.c commits. I noticed this because Clang warns now:

mm/migrate.c:347:14: error: variable 'ptl' is uninitialized when used here [-Werror,-Wuninitialized]
        spin_unlock(ptl);
                    ^~~
mm/migrate.c:340:17: note: initialize the variable 'ptl' to silence this warning
        spinlock_t *ptl;
                       ^
                        = NULL
1 error generated.

Cheers,
Nathan

Re: linux-next: Tree for Dec 14 (arch/x86/kernel/apic/msi.o)

[Randy Dunlap]

[-- Attachment #1: Type: text/plain, Size: 398 bytes --]



On 12/14/21 14:32, broonie@kernel.org wrote:
> Hi all,
> 
> News: Releases may or may not happen over the next few days since I'm
> getting a vacciene dose tomorrow.
> 
> Changes since 20211213:
> 

on x86_64:

ld: arch/x86/kernel/apic/msi.o: in function `arch_restore_msi_irqs':
msi.c:(.text+0x245): undefined reference to `xen_initdom_restore_msi'

Full randconfig file is attached.

-- 
~Randy

[-- Attachment #2: config-r1890.gz --]
[-- Type: application/gzip, Size: 39848 bytes --]

Re: linux-next: Tree for Dec 14 (arch/x86/kernel/apic/msi.o)

[Thomas Gleixner]

On Tue, Dec 14 2021 at 17:49, Randy Dunlap wrote:
> On 12/14/21 14:32, broonie@kernel.org wrote:
>> Hi all,
>> 
>> News: Releases may or may not happen over the next few days since I'm
>> getting a vacciene dose tomorrow.
>> 
>> Changes since 20211213:
>> 
>
> on x86_64:
>
> ld: arch/x86/kernel/apic/msi.o: in function `arch_restore_msi_irqs':
> msi.c:(.text+0x245): undefined reference to `xen_initdom_restore_msi'

Fixed. Arnd sent a patch already.

Thanks,

        tglx

Re: linux-next: Tree for Dec 14

[Andy Shevchenko]

On Tue, Dec 14, 2021 at 10:32:22PM +0000, broonie@kernel.org wrote:
> Hi all,
> 
> News: Releases may or may not happen over the next few days since I'm
> getting a vacciene dose tomorrow.
> 
> Changes since 20211213:

> The drm-intel tree gained a conflict with the drm-intel-fixes tree.
> 
> The dmaengine tree gained a conflict with the dmaengine-fixes tree.
> 
> Non-merge commits (relative to Linus' tree): 6251
>  6873 files changed, 291130 insertions(+), 138903 deletions(-)

Thanks, I see tags now.

The other issue I have noticed is that gpio-intel branches [1] are out of the
merge. I haven't got any email about any issues with them.

Do you have the latest and greatest list of repositories to merge?

[1]: For example in next-20211203

e24d0a695952 Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/andy/linux-gpio-intel.git


-- 
With Best Regards,
Andy Shevchenko

Re: linux-next: Tree for Dec 14

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 782 bytes --]

On Wed, Dec 15, 2021 at 05:54:55PM +0200, Andy Shevchenko wrote:

Please note that due to people replying with random bug reports against
the actual code in -next replying to the -next message isn't a super
good way of getting my attention you can get lost in the noise.

> Thanks, I see tags now.

I fixed the bug with the script, it doesn't check for errors when
tagging unfortunately.

> The other issue I have noticed is that gpio-intel branches [1] are out of the
> merge. I haven't got any email about any issues with them.

> Do you have the latest and greatest list of repositories to merge?

You can see in the merge log that it's getting skipped due to an issue
with the previous tree (which also has a build failure causing me to
need to revert it) upsetting the script.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: Tree for Dec 14

[Andy Shevchenko]

On Wed, Dec 15, 2021 at 06:06:03PM +0000, Mark Brown wrote:
> On Wed, Dec 15, 2021 at 05:54:55PM +0200, Andy Shevchenko wrote:

> > The other issue I have noticed is that gpio-intel branches [1] are out of the
> > merge. I haven't got any email about any issues with them.
> 
> > Do you have the latest and greatest list of repositories to merge?
> 
> You can see in the merge log that it's getting skipped due to an issue
> with the previous tree (which also has a build failure causing me to
> need to revert it) upsetting the script.

Yes, I see now. But as far as I know my repo doesn't have issues (neither
compilation nor merge), or at least nobody so far informed me about.

-- 
With Best Regards,
Andy Shevchenko

Re: linux-next: Tree for Dec 14

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 545 bytes --]

On Wed, Dec 15, 2021 at 08:40:11PM +0200, Andy Shevchenko wrote:
> On Wed, Dec 15, 2021 at 06:06:03PM +0000, Mark Brown wrote:

> > You can see in the merge log that it's getting skipped due to an issue
> > with the previous tree (which also has a build failure causing me to
> > need to revert it) upsetting the script.

> Yes, I see now. But as far as I know my repo doesn't have issues (neither
> compilation nor merge), or at least nobody so far informed me about.

Like I say it's an issue with the *previous* tree which upsets the
script.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]