This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/60/29960/1
in repository toolchain/jenkins-scripts.
discards f6341cc81 tcwg_kernel/*: Remove unused configuration files.
new 04372f58b tcwg_kernel/*: Remove unused configuration files.
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (f6341cc81)
\
N -- N -- N refs/changes/60/29960/1 (04372f58b)
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:
--
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.
maxim.kuvyrkov pushed a change to reference refs/changes/59/47259/4
in repository toolchain/jenkins-scripts.
discards e96fef0b6 tcwg_update_components_revs.sh: Create script to update the c [...]
adds cafa6a678 tcwg_update_components_revs.sh: Create script to update the c [...]
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (e96fef0b6)
\
N -- N -- N refs/changes/59/47259/4 (cafa6a678)
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.
No new revisions were added by this update.
Summary of changes:
--
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.
maxim.kuvyrkov pushed a change to reference refs/changes/59/47259/3
in repository toolchain/jenkins-scripts.
discards e745d92bb tcwg_update_components_revs.sh: Create script to update the c [...]
adds 62c5a3007 tcwg_update_components_revs.sh: Create script to update the c [...]
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (e745d92bb)
\
N -- N -- N refs/changes/59/47259/3 (62c5a3007)
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.
No new revisions were added by this update.
Summary of changes:
--
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.
maxim.kuvyrkov pushed a change to reference refs/changes/59/47259/2
in repository toolchain/jenkins-scripts.
discards 64f0e59c4 tcwg_update_components_revs.sh: Create script to update the c [...]
adds 8a69c2e01 tcwg_update_components_revs.sh: Create script to update the c [...]
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (64f0e59c4)
\
N -- N -- N refs/changes/59/47259/2 (8a69c2e01)
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.
No new revisions were added by this update.
Summary of changes:
--
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.
maxim.kuvyrkov pushed a change to reference refs/changes/59/47259/1
in repository toolchain/jenkins-scripts.
discards 12b4ce98d tcwg_update_components_revs.sh: Create script to update the c [...]
adds 319db6982 tcwg_update_components_revs.sh: Create script to update the c [...]
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (12b4ce98d)
\
N -- N -- N refs/changes/59/47259/1 (319db6982)
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.
No new revisions were added by this update.
Summary of changes:
--
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.
maxim.kuvyrkov pushed a change to reference refs/changes/59/47159/1
in repository toolchain/jenkins-scripts.
discards a2171c839 round-robin-bisect.sh: use extra-build-parameter to pass xxx_ [...]
discards f4e76aa62 tcwg_bmk-build.sh: upgrade fujitsu projects
adds 55beab9e1 tcwg_bmk-build.sh: upgrade fujitsu projects
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (a2171c839)
\
N -- N -- N refs/changes/59/47159/1 (55beab9e1)
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.
No new revisions were added by this update.
Summary of changes:
round-robin-baseline.sh | 650 -------------
round-robin-bisect.sh | 689 --------------
round-robin-notify.sh | 2414 -----------------------------------------------
3 files changed, 3753 deletions(-)
delete mode 100755 round-robin-baseline.sh
delete mode 100755 round-robin-bisect.sh
delete mode 100755 round-robin-notify.sh
--
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.
maxim.kuvyrkov pushed a change to reference refs/changes/59/47059/1
in repository toolchain/jenkins-scripts.
discards cf94ba063 tcwg-lnt/tcwg-lnt-*/config: Update tcwg_gnu_mingw_* project names
adds 1982b184e tcwg-lnt/tcwg-lnt-*/config: Update tcwg_gnu_mingw_* project names
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (cf94ba063)
\
N -- N -- N refs/changes/59/47059/1 (1982b184e)
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.
No new revisions were added by this update.
Summary of changes:
--
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.
maxim.kuvyrkov pushed a change to reference refs/changes/59/46559/1
in repository toolchain/jenkins-scripts.
discards e5c928a52 tcwg_aosp-build.sh: fix typo from previous commit
adds 0f5665b38 tcwg_aosp-build.sh: fix typo from previous commit
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (e5c928a52)
\
N -- N -- N refs/changes/59/46559/1 (0f5665b38)
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.
No new revisions were added by this update.
Summary of changes:
--
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.
maxim.kuvyrkov pushed a change to reference refs/changes/59/46459/7
in repository toolchain/jenkins-scripts.
discards 29a68e334 precommit-test.sh: New script to test each patch in a series
adds 107149560 precommit-test.sh: New script to test each patch in a series
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (29a68e334)
\
N -- N -- N refs/changes/59/46459/7 (107149560)
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.
No new revisions were added by this update.
Summary of changes:
--
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 786c8248dbd3 Merge tag 'perf-tools-fixes-for-v6.11-2024-07-23' of git:/ [...]
new e44be00289ef hostfs: fix folio conversion
new a9d47a50cf25 netfs: Revert "netfs: Switch debug logging to pr_debug()"
new fcad93360df4 netfs: Rename CONFIG_FSCACHE_DEBUG to CONFIG_NETFS_DEBUG
new 5bc9ad78c2f8 vfs: handle __wait_on_freeing_inode() and evict() race
new b40c8e7a033f vfs: correct the comments of vfs_*() helpers
new f60d38cb02d0 pidfs: when time ns disabled add check for ioctl
new 9b3e15046437 pidfs: handle kernels without namespaces cleanly
new 1bb8dce5dfa9 pidfs: add selftests for new namespace ioctls
new 212be98aa193 netfs: Fix writeback that needs to go to both server and cache
new 51d37982bbac cachefiles: Set the max subreq size for cache writes to MA [...]
new 8eac5358ad3b fs: use all available ids
new f8138f2ad2f7 filelock: Fix fcntl/close race recovery compat path
new c3a5e3e872f3 vfs: Fix potential circular locking through setxattr() and [...]
new f5e5e97c719d inode: clarify what's locked
new d1e9a63dcd72 Merge tag 'vfs-6.11-rc1.fixes.2' of git://git.kernel.org/p [...]
The 15 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:
fs/cachefiles/io.c | 2 +-
fs/hostfs/hostfs_kern.c | 2 +-
fs/inode.c | 40 +++-
fs/locks.c | 9 +-
fs/namei.c | 26 +--
fs/namespace.c | 2 +-
fs/netfs/Kconfig | 18 +-
fs/netfs/buffered_read.c | 14 +-
fs/netfs/buffered_write.c | 12 +-
fs/netfs/direct_read.c | 2 +-
fs/netfs/direct_write.c | 8 +-
fs/netfs/fscache_cache.c | 4 +-
fs/netfs/fscache_cookie.c | 28 +--
fs/netfs/fscache_io.c | 12 +-
fs/netfs/fscache_main.c | 2 +-
fs/netfs/fscache_volume.c | 4 +-
fs/netfs/internal.h | 33 ++-
fs/netfs/io.c | 12 +-
fs/netfs/main.c | 4 +
fs/netfs/misc.c | 4 +-
fs/netfs/write_collect.c | 16 +-
fs/netfs/write_issue.c | 37 ++--
fs/pidfs.c | 63 ++++--
fs/xattr.c | 91 ++++----
tools/testing/selftests/pidfd/pidfd_setns_test.c | 258 ++++++++++++++++++++---
25 files changed, 489 insertions(+), 214 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.