From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 88B7CCD11C2 for ; Fri, 5 Apr 2024 05:55:24 +0000 (UTC) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=leemhuis.info header.i=@leemhuis.info header.a=rsa-sha256 header.s=he214686 header.b=yu6iAYkl; dkim-atps=neutral Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4V9nlH1H1lz3vbF for ; Fri, 5 Apr 2024 16:55:23 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=leemhuis.info header.i=@leemhuis.info header.a=rsa-sha256 header.s=he214686 header.b=yu6iAYkl; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=leemhuis.info (client-ip=80.237.130.52; helo=wp530.webpack.hosteurope.de; envelope-from=regressions@leemhuis.info; receiver=lists.ozlabs.org) Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4V9nkR6RWqz3dW4 for ; Fri, 5 Apr 2024 16:54:38 +1100 (AEDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=leemhuis.info; s=he214686; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:From:References:Cc:To:Subject:MIME-Version:Date:Message-ID:From: Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:In-Reply-To: References; bh=5+CSatVUX1mB5iLzA7Er8OGguj0pB7lpB5xhAhk7j8k=; t=1712296480; x=1712728480; b=yu6iAYklQY0ixCIy10FMR0RamVOVnivbyA2pM4h237pRCza0fhEe07bjIpsfC h0ojIwhALP4NDXY0R75rMMlZYkZbTupLUR81pshLhPtMXN2/YhPM+2OmLLB9Ousu/afHGk9aKPWwf 3dvYwWPfUsVevTaHy6QVz4zw+5uJlrXq3jjnn0n+LclCUxcPxJIk9YIQfagivLz7286gRObN3cELY v4zLOqQlPNDFxXWKe0GiNEXEuI2Ws1Czge7jtJ2cu3kTbumx7y0IRwIm9Lm0qNtKKvHCAUbJCfF4a a6fEbvoBLu7KSTF0h+ZgLRsDSiLt0j6OZC6SmOxLlJegA9qWow==; Received: from [2a02:8108:8980:2478:8cde:aa2c:f324:937e]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1rscX3-00021j-El; Fri, 05 Apr 2024 07:54:33 +0200 Message-ID: Date: Fri, 5 Apr 2024 07:54:32 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] KVM: PPC: Book3S HV nestedv2: Cancel pending HDEC exception To: Michael Ellerman , Nicholas Piggin , Vaibhav Jain , linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org References: <20240313072625.76804-1-vaibhav@linux.ibm.com> <87sf007ax6.fsf@mail.lhotse> From: Thorsten Leemhuis Content-Language: en-US, de-DE In-Reply-To: <87sf007ax6.fsf@mail.lhotse> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1712296480;c29130a1; X-HE-SMSGID: 1rscX3-00021j-El X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: mikey@neuling.org, Linux kernel regressions list , sbhat@linux.ibm.com, amachhiw@linux.vnet.ibm.com, Jordan Niethe , gautam@linux.ibm.com, David.Laight@ACULAB.COM, kconsul@linux.vnet.ibm.com, Vaidyanathan Srinivasan Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On 05.04.24 05:20, Michael Ellerman wrote: > "Linux regression tracking (Thorsten Leemhuis)" > writes: >> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting >> for once, to make this easily accessible to everyone. >> >> Was this regression ever resolved? Doesn't look like it, but maybe I >> just missed something. > > I'm not sure how it ended up on the regression list. That is easy to explain: I let lei search for mails containing words like regress, bisect, and revert to become aware of regressions that might need tracking. And... > IMHO it's not really a regression. ...sometimes I misjudge or misinterpret something and add it to the regression tracking. Looks like that happened here. Sorry for that and the noise it caused! #regzbot resolve: invalid: was not really a regression in the first place Ciao, Thorsten