stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: CKI <cki-project@redhat.com>
To: Linux Stable maillist <stable@vger.kernel.org>
Subject: Stable queue: queue-4.20
Date: Mon, 21 Jan 2019 09:22:36 -0500	[thread overview]
Message-ID: <cki.BD61AAC50297497C0E559077D472F74FC28B036B7D9689C64A976FEE953738BC.WV2BMWLHJQ6KO5UE5BOCI4DQXF19LPYFP86S00K9@redhat.com> (raw)

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

Hello,

We ran automated tests on a patchset that was proposed for merging into this
kernel tree. The patches were applied to:

       Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
            Commit: e9a713f77bb2 Linux 4.20.3

The results of these automated tests are provided below.

    Overall result: PASSED
       Patch merge: OK
           Compile: OK
      Kernel tests: OK

Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.

        ,-.   ,-.
       ( C ) ( K )  Continuous
        `-',-.`-'   Kernel
          ( I )     Integration
           `-'
______________________________________________________________________________

Merge testing
-------------

We cloned this repository and checked out a ref:

  Repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
  Ref:  e9a713f77bb2 Linux 4.20.3

We then merged the following patches with `git am`:

  tty-ldsem-wake-up-readers-after-timed-out-down_write.patch
  tty-hold-tty_ldisc_lock-during-tty_reopen.patch
  tty-simplify-tty-count-math-in-tty_reopen.patch
  tty-don-t-hold-ldisc-lock-in-tty_reopen-if-ldisc-present.patch
  can-gw-ensure-dlc-boundaries-after-can-frame-modification.patch
  netfilter-nf_conncount-replace-conncount_lock_slots-with-conncount_slots.patch
  netfilter-nf_conncount-don-t-skip-eviction-when-age-is-negative.patch
  netfilter-nf_conncount-split-gc-in-two-phases.patch
  netfilter-nf_conncount-restart-search-when-nodes-have-been-erased.patch
  netfilter-nf_conncount-merge-lookup-and-add-functions.patch
  netfilter-nf_conncount-move-all-list-iterations-under-spinlock.patch
  netfilter-nf_conncount-speculative-garbage-collection-on-empty-lists.patch
  netfilter-nf_conncount-fix-argument-order-to-find_next_bit.patch
  mmc-sdhci-msm-disable-cdr-function-on-tx.patch
  arm64-kvm-consistently-handle-host-hcr_el2-flags.patch
  arm64-don-t-trap-host-pointer-auth-use-to-el2.patch
  ipv6-fix-kernel-infoleak-in-ipv6_local_error.patch
  net-bridge-fix-a-bug-on-using-a-neighbour-cache-entry-without-checking-its-state.patch
  packet-do-not-leak-dev-refcounts-on-error-exit.patch
  tcp-change-txhash-on-syn-data-timeout.patch
  tun-publish-tfile-after-it-s-fully-initialized.patch
  net-phy-add-missing-phy-driver-features.patch
  net-phy-add-missing-features-to-phy-drivers.patch
  net-phy-meson-gxl-use-the-genphy_soft_reset-callback.patch
  lan743x-remove-phy_read-from-link-status-change-function.patch
  in_badclass-fix-macro-to-actually-work.patch
  r8169-load-realtek-phy-driver-module-before-r8169.patch
  bonding-update-nest-level-on-unlink.patch
  ip-on-queued-skb-use-skb_header_pointer-instead-of-pskb_may_pull.patch
  r8169-don-t-try-to-read-counters-if-chip-is-in-a-pci-power-save-state.patch
  smc-move-unhash-as-early-as-possible-in-smc_release.patch

Compile testing
---------------

We compiled the kernel for 0 architecture:


             reply	other threads:[~2019-01-21 14:22 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 14:22 CKI [this message]
2019-01-21 15:35 ` Stable queue: queue-4.20 Major Hayden
  -- strict thread matches above, loose matches on Subject: below --
2019-03-07 21:21 CKI
2019-03-03 23:14 CKI
2019-03-03 13:27 CKI
2019-03-03  6:10 CKI
2019-02-28 22:21 CKI
2019-02-27 12:19 CKI
2019-02-27  1:09 CKI
2019-02-26 13:33 CKI
2019-02-26  8:09 CKI
2019-02-26  7:10 CKI
2019-02-26  5:58 CKI
2019-02-25  1:19 CKI
2019-02-24 23:15 CKI
2019-02-18 19:49 CKI
2019-02-18 17:40 CKI
2019-02-18 10:50 CKI
2019-02-18  7:45 CKI
2019-02-15 23:42 CKI
2019-02-12 12:38 CKI
2019-02-11 21:27 CKI
2019-02-11 21:26 CKI
2019-02-11 18:42 CKI
2019-02-11 17:58 CKI
2019-02-10 17:20 CKI
2019-02-10 16:54 CKI
2019-02-10 15:40 CKI
2019-02-09 23:20 CKI
2019-02-04 11:34 CKI
2019-02-04  6:26 CKI
2019-02-04  7:24 ` Greg KH
2019-02-06  9:51   ` Nikolai Kondrashov
2019-02-02 19:20 CKI
2019-02-02 12:55 CKI
2019-01-31 22:12 CKI
2019-01-30  8:03 CKI
2019-01-30  8:16 ` Greg KH
2019-01-30  9:10   ` Major Hayden
2019-01-28 21:36 CKI
2019-01-29  7:41 ` Nikolai Kondrashov
2019-01-29  7:48   ` Nikolai Kondrashov
2019-01-28 21:36 CKI
2019-01-28 13:37 CKI
2019-01-27 22:47 CKI
2019-01-27 22:30 CKI
2019-01-26 21:50 CKI
2019-01-26 11:39 CKI
2019-01-25 14:32 CKI
2019-01-25  0:39 CKI
2019-01-24 22:37 CKI
2019-01-23 21:09 CKI
2019-01-21 23:18 CKI
2019-01-21 18:10 CKI
2019-01-18 23:36 CKI
2019-01-18  6:09 CKI
2019-01-14 15:16 CKI
2019-01-14 16:22 ` Greg KH
2019-01-11 10:54 CKI
2019-01-11  3:16 CKI
2019-01-10 22:04 CKI
2019-01-10 20:51 CKI
2019-01-10 18:52 CKI
2019-01-10 16:43 CKI
2019-01-08 22:31 CKI
2019-01-09 14:39 ` Greg KH
2019-01-09 14:48   ` Major Hayden

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cki.BD61AAC50297497C0E559077D472F74FC28B036B7D9689C64A976FEE953738BC.WV2BMWLHJQ6KO5UE5BOCI4DQXF19LPYFP86S00K9@redhat.com \
    --to=cki-project@redhat.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).