This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 9fa6c59a 4: update: qemu-7b09f127738ae3d0e71716cea086fc8f847a5686: 22
discards 98704ae4 3: reset: linux-qemu: 22
discards 4f0d55ba 2: update: binutils-gcc-qemu: 21239
new f4e7ed5a 2: update: linux-ef8b014ee4a1ccd9e751732690a8c7cdeed945e7: 21258
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (9fa6c59a)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-ne [...]
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
01-reset_artifacts/console.log | 181 +-
02-prepare_abe/console.log | 444 +-
03-build_abe-binutils/console.log | 10145 ++++----
04-build_abe-stage1/console.log | 19208 +++++++--------
05-build_linux/console.log | 7597 +-----
08-check_regression/console.log | 30 +-
08-check_regression/results.regressions | 20 +-
09-update_baseline/console.log | 220 +-
09-update_baseline/results.regressions | 20 +-
console.log | 37837 +++++++++++++-----------------
jenkins/manifest.sh | 10 +-
results | 2 +-
12 files changed, 31792 insertions(+), 43922 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch master
in repository linux.
from 7c53f6b671f4 Linux 5.11-rc3
new dfe94d4086e4 x86/hyperv: Fix kexec panic/hang issues
new ad0a6bad4475 x86/hyperv: check cpu mask after interrupt has been disabled
new f1ee3e150bd9 Merge tag 'hyperv-fixes-signed-20210111' of git://git.kern [...]
new 72d78717c6d0 nfsd: Fixes for nfsd4_encode_read_plus_data()
new b68f0cbd3f95 nfsd: Don't set eof on a truncated READ_PLUS
new d6c9e4368cc6 NFSD: Fix sparse warning in nfssvc.c
new 4a85a6a3320b SUNRPC: Handle TCP socket sends with kernel_sendpage() again
new 7b723008f9c9 NFSD: Restore NFSv4 decoding's SAVEMEM functionality
new c912fd05fab9 Merge tag 'nfsd-5.11-1' of git://git.linux-nfs.org/project [...]
The 9 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
arch/x86/hyperv/hv_init.c | 4 ++
arch/x86/hyperv/mmu.c | 12 ++++--
arch/x86/include/asm/mshyperv.h | 2 +
arch/x86/kernel/cpu/mshyperv.c | 18 +++++++++
drivers/hv/vmbus_drv.c | 2 -
fs/nfsd/nfs4proc.c | 5 +++
fs/nfsd/nfs4xdr.c | 56 +++++++++++++++++----------
fs/nfsd/nfssvc.c | 6 ---
fs/nfsd/xdr4.h | 1 -
net/sunrpc/svcsock.c | 86 ++++++++++++++++++++++++++++++++++++++++-
10 files changed, 159 insertions(+), 33 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allyesconfig
in repository toolchain/ci/base-artifacts.
discards d233e0da 0: update: binutils-gcc-linux-qemu: all
new 7361ceba 0: update: linux-0b0e7c53418e746aa23e11c174f7040c2a381277: all
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (d233e0da)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-aarch6 [...]
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
01-reset_artifacts/console.log | 161 +-
02-prepare_abe/console.log | 438 +-
03-build_abe-binutils/console.log | 11815 ++++----
04-build_abe-stage1/console.log | 16272 ++++++-----
05-build_linux/console.log | 9403 +++----
06-build_abe-qemu/console.log | 6716 +++--
07-boot_linux/console.log | 6 +-
08-check_regression/console.log | 14 +-
08-check_regression/results.regressions | 2 +-
09-update_baseline/console.log | 12 +-
09-update_baseline/results.regressions | 2 +-
console.log | 44743 +++++++++++++++---------------
jenkins/manifest.sh | 16 +-
results | 2 +-
14 files changed, 44043 insertions(+), 45559 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-next-defconfig
in repository toolchain/ci/base-artifacts.
discards 1ad2a343 0: update: llvm-linux-qemu: boot
new 63206c2c 0: update: llvm-linux-qemu: boot
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (1ad2a343)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-arm- [...]
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
01-reset_artifacts/console.log | 30 +-
02-prepare_abe/console.log | 438 +-
03-build_llvm/console.log | 13247 +++++++++++++--------------
04-build_linux/console.log | 664 +-
05-build_abe-qemu/console.log | 3892 ++++----
06-boot_linux/console.log | 488 +-
07-check_regression/console.log | 4 +-
08-update_baseline/console.log | 4 +-
console.log | 18767 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
results | 2 +-
11 files changed, 18771 insertions(+), 18773 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch master
in repository glibc.
from bf7db6d369 math: Add BZ#18980 fix back on dbl-64 cosh
new 87d583c6e8 install: Replace scripts/output-format.sed with objdump -f [ [...]
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
Makerules | 13 +++-------
benchtests/strcoll-inputs/filelist#en_US.UTF-8 | 1 -
config.make.in | 1 -
configure | 19 --------------
configure.ac | 11 --------
scripts/output-format.sed | 35 --------------------------
6 files changed, 3 insertions(+), 77 deletions(-)
delete mode 100644 scripts/output-format.sed
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 1b42ec99 0: update: llvm-linux-qemu: boot
new 07cadbd7 0: update: llvm-linux-qemu: boot
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (1b42ec99)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-aarch [...]
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
01-reset_artifacts/console.log | 162 +-
02-prepare_abe/console.log | 434 +-
03-build_llvm/console.log | 13832 ++++++++++++------------
04-build_linux/console.log | 802 +-
05-build_abe-qemu/console.log | 6709 ++++++------
06-boot_linux/console.log | 4 +-
07-check_regression/console.log | 2 +-
08-update_baseline/console.log | 2 +-
console.log | 21947 +++++++++++++++++++-------------------
jenkins/manifest.sh | 12 +-
10 files changed, 21946 insertions(+), 21960 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.