From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751515AbdFGC01 (ORCPT <rfc822;w@1wt.eu>);
        Tue, 6 Jun 2017 22:26:27 -0400
Received: from mout.gmx.net ([212.227.15.15]:64288 "EHLO mout.gmx.net"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751474AbdFGC0Z (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 6 Jun 2017 22:26:25 -0400
Message-ID: <1496802359.12728.15.camel@gmx.de>
Subject: Re: [lkp-robot] [tty]  52b03e644f: calltrace:flush_to_ldisc
From: Mike Galbraith <efault@gmx.de>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Vegard Nossum <vegard.nossum@oracle.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Dave Jones <davej@codemonkey.org.uk>,
        Linux Kernel <linux-kernel@vger.kernel.org>,
        Jiri Slaby <jslaby@suse.com>, lkp@01.org
Date: Wed, 07 Jun 2017 04:25:59 +0200
In-Reply-To: <20170607020738.GF2969@yexl-desktop>
References: <20170607020738.GF2969@yexl-desktop>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.20.5 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:xqSBw2EWJ2q1GGD/FW6baMnkty93THODWNybXPGquBO0I50oUa8
 ho3F0MuqBGeww2qkrKTNCHP/nPEplgahFvF7Aa8ff1R1jFGnyRWB6XvPzVl2fImWV3aOTU1
 t4K/LnLQnmkQLbAe6F8c1KwXSKckObl0aYiX85Zpw98omSUGmeFU4kPv7Hp98q0oGwrJ08t
 rOTrHMsNg7ozyGt+8/5vQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:koJCxlDITJ4=:EHoYvDibk5mdY30BH+xqHf
 QUZwiJN/sS68kNSbDoylng5aldeXz1opcoBW/V3t1THgB6GqJblpi1cOjkPqlZjOR02PDPSKH
 k/v+BHKSbscnWR0AAC0RiLe/F7O28nXETKGL5t12W3bToDAwkz+xtxIA8fOTpHJU641LoHEWn
 5h+gxtHpAl4PA41dh5e03G/cp9Y55KPEByjH94zy4xia1t0zBX2g644hjYrLi49O6BsQzefZD
 Ukp19rzScCC4A1+ufCkgYLYJ//+3CZpMHgIP7tiBJjP9BRS6NFZj1lQfxo0ynn/CXuTaFXuOM
 b/QE3cdwg973lfr9W1sTB2qdw33VxkywXXcrP3FVxqLcTbFIuFaL40r2rvYNzL1Dv4txId7rW
 ldbqczKNh6Hij412+uNtN7NY1Sg98SJGH4aIUaUioWrEkHoAR/buBb+iuvSOjZIJDZwHGw/++
 OL4q1RvfP01AZPAbCUqZYt4KOZa8PCyWw+T9BrQoSMz1xxLwcOTQ96rtMtVvkTrW6WgQlZYzn
 zBgtcgT8QZgcPEvxHcmswAqVZRtUz/riNXnF+51GWbzAIqlZTRzv5wKT8Aaa1DxyCd86MD5fI
 WsSZaR619ZBw/Jhv82NHJlcZvXcKMb1iI6qvQcCuk0bkffv9LLYvylrRYmDgSDy5uhwwx0T/G
 be11Hi9SXjPWcb78gZbikpAmKUBAWJXqS0HtNciVMDIEOx7Leriwzk5TIJ4UFV3mhLfISnP3f
 jhM3ZOpsFLnc5Dnn3fSBhxzXownztj4EHnKxaFhdVrN1b/NOzbab1qhcN4lmg1u2dQhTfTa/x
 +H3vXwu
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, 2017-06-07 at 10:07 +0800, kernel test robot wrote:
> FYI, we noticed the following commit:
> 
> commit: 52b03e644f702dbcb252f6aec92fc0f0d6e29f78 ("tty: fix port buffer locking V2")
> url: https://github.com/0day-ci/linux/commits/Mike-Galbraith/tty-fix-port-buffer-locking-V2/20170605-134432
> base: https://git.kernel.org/cgit/linux/kernel/git/gregkh/tty.git tty-testing

?  Patchlet has been properly vaporized, no longer exists.

	-Mike