This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch master
in repository linux.
from e71ba9452f0b Linux 5.11-rc2
new 196793946264 Compiler Attributes: remove CONFIG_ENABLE_MUST_CHECK
new f4f6a2e32952 Merge tag 'compiler-attributes-for-linus-v5.11' of git://g [...]
new 1b04fa990026 rcu-tasks: Move RCU-tasks initialization to before early_i [...]
new 36bbbd0e234d Merge branch 'rcu/urgent' of git://git.kernel.org/pub/scm/ [...]
The 4 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:
include/linux/compiler_attributes.h | 6 ++++++
include/linux/compiler_types.h | 6 ------
include/linux/rcupdate.h | 6 ++++++
init/main.c | 1 +
kernel/rcu/tasks.h | 25 ++++++++++++++++++----
lib/Kconfig.debug | 8 -------
.../testing/selftests/wireguard/qemu/debug.config | 1 -
7 files changed, 34 insertions(+), 19 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-release-aarch64-stable-allmodconfig
in repository toolchain/ci/base-artifacts.
discards a98c65920 0: update: binutils-gcc-linux-qemu: boot
new db6c16c52 0: update: gcc-a8a453d82e2c2ce04f40742327033214b9d3582c: 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 (a98c65920)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-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 | 130 +-
02-prepare_abe/console.log | 445 +-
03-build_abe-binutils/console.log | 10935 +++++------
04-build_abe-stage1/console.log | 13975 +++++++-------
05-build_linux/console.log | 601 +-
06-build_abe-qemu/console.log | 4435 ++---
07-boot_linux/console.log | 8 +-
08-check_regression/console.log | 2 +-
08-check_regression/results.regressions | 2 +-
09-update_baseline/console.log | 10 +-
09-update_baseline/results.regressions | 2 +-
console.log | 30999 +++++++++++++++---------------
jenkins/manifest.sh | 18 +-
13 files changed, 29983 insertions(+), 31579 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-master-aarch64-mainline-defconfig
in repository toolchain/ci/base-artifacts.
discards 16062b332 0: update: llvm-linux-qemu: boot
new 4e103d674 0: update: llvm-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 (16062b332)
\
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 | 70 +-
02-prepare_abe/console.log | 217 +-
03-build_llvm/console.log | 13856 ++++++++++++------------
04-build_linux/console.log | 549 +-
05-build_abe-qemu/console.log | 6733 ++++++------
06-boot_linux/console.log | 494 +-
07-check_regression/console.log | 56 +-
08-update_baseline/console.log | 20 +-
console.log | 21995 +++++++++++++++++++-------------------
jenkins/manifest.sh | 14 +-
10 files changed, 21868 insertions(+), 22136 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-mainline-defconfig
in repository toolchain/ci/base-artifacts.
discards 8932e65eb 0: update: llvm-linux-qemu: boot
new 5a1342adf 0: update: llvm-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 (8932e65eb)
\
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 | 26 +-
02-prepare_abe/console.log | 439 +-
03-build_llvm/console.log | 13210 +++++++++++++-------------
04-build_linux/console.log | 547 +-
05-build_abe-qemu/console.log | 4620 ++++-----
06-boot_linux/console.log | 494 +-
07-check_regression/console.log | 4 +-
08-update_baseline/console.log | 10 +-
console.log | 19378 +++++++++++++++++++-------------------
jenkins/manifest.sh | 10 +-
10 files changed, 19255 insertions(+), 19483 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-release-arm-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards ad956e3fb 0: update: binutils-gcc-linux-qemu: all
new e00f00e1e 0: update: qemu-386b2a5767f7642521cd07930c681ec8a6057e60: 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 (ad956e3fb)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-arm-n [...]
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 | 235 +-
02-prepare_abe/console.log | 439 +-
03-build_abe-binutils/console.log | 10835 +++++----
04-build_abe-stage1/console.log | 18289 ++++++++--------
05-build_linux/console.log | 570 +-
06-build_abe-qemu/console.log | 4621 ++--
07-boot_linux/console.log | 6 +-
08-check_regression/console.log | 16 +-
08-check_regression/results.regressions | 2 +-
09-update_baseline/console.log | 22 +-
09-update_baseline/results.regressions | 2 +-
console.log | 35043 +++++++++++++++---------------
jenkins/manifest.sh | 14 +-
13 files changed, 34329 insertions(+), 35765 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-release-aarch64-lts-allmodconfig
in repository toolchain/ci/base-artifacts.
discards f26dfb9af 0: update: binutils-gcc-linux-qemu: boot
new 9727b6cf4 0: update: gcc-a8a453d82e2c2ce04f40742327033214b9d3582c: 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 (f26dfb9af)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-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 | 226 +-
02-prepare_abe/console.log | 441 +-
03-build_abe-binutils/console.log | 11405 ++++++-----
04-build_abe-stage1/console.log | 13947 ++++++-------
05-build_linux/console.log | 635 +-
06-build_abe-qemu/console.log | 4431 ++---
07-boot_linux/console.log | 8 +-
08-check_regression/console.log | 18 +-
08-check_regression/results.regressions | 2 +-
09-update_baseline/console.log | 12 +-
09-update_baseline/results.regressions | 2 +-
console.log | 31123 +++++++++++++++---------------
jenkins/manifest.sh | 18 +-
13 files changed, 30346 insertions(+), 31922 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 binutils-gdb.
from 3ec3145c5dd gdb: introduce scoped debug prints
new e4ad960a577 [gdb/symtab] Remove superfluous end-of-sequence marker
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:
gdb/ChangeLog | 5 ++++
gdb/buildsym.c | 9 ++++--
gdb/testsuite/ChangeLog | 4 +++
...-opcode.exp => dw2-out-of-range-end-of-seq.exp} | 35 +++++++++++++++-------
4 files changed, 40 insertions(+), 13 deletions(-)
copy gdb/testsuite/gdb.dwarf2/{dw2-vendor-extended-opcode.exp => dw2-out-of-range- [...]
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.