This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch mmu_gather-race-fix in repository linux.
discards db12063aab49 mm: delay rmap removal until after TLB flush discards d12cec60e0fc mm: re-unify the simplified page_zap_*_rmap() function discards 4305e9c77151 mm: inline simpler case of page_remove_file_rmap() discards e2dd770a9425 mm: introduce simplified versions of 'page_remove_rmap()' new 62f70d93f7f3 mm: introduce simplified versions of 'page_remove_rmap()' new 87f9406d812f mm: inline simpler case of page_remove_file_rmap() new 655d4bdee635 mm: re-unify the simplified page_zap_*_rmap() function new 9c7aff0cbe3d mm: delay rmap removal until after TLB flush
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 (db12063aab49) \ N -- N -- N refs/heads/mmu_gather-race-fix (9c7aff0cbe3d)
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 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: