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 X-Spam-Level: X-Spam-Status: No, score=-8.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E6AF1C64E7A for ; Tue, 1 Dec 2020 12:09:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 799DD2084C for ; Tue, 1 Dec 2020 12:09:07 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="dGQXU55H" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727888AbgLAMJH (ORCPT ); Tue, 1 Dec 2020 07:09:07 -0500 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:42348 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727070AbgLAMJG (ORCPT ); Tue, 1 Dec 2020 07:09:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1606824460; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=PXfc/kqkacP1UiqS7nvKt7QqE8tU45M98d6kX6CKfRY=; b=dGQXU55HFWtwAM1XWDqS48zAdfz+Q9yNytlel86KShSs25y049xBYDVKXn+q/hz5h75Xw9 Y0kZBbn7HMPk4K7bojIeLldJPO2ra/DNsCeUdb2wFWsShQCtzKeRRKzd+TnUT0pJmwWYXT 1jTtHcNSzJlfNQprsG2EYj4A8glXVtw= Received: from mail-ed1-f72.google.com (mail-ed1-f72.google.com [209.85.208.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-157-1EZSgYHuPoiv3Lp5P53Ryw-1; Tue, 01 Dec 2020 07:07:38 -0500 X-MC-Unique: 1EZSgYHuPoiv3Lp5P53Ryw-1 Received: by mail-ed1-f72.google.com with SMTP id f19so1106454edq.20 for ; Tue, 01 Dec 2020 04:07:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:cc:references:from:subject:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=PXfc/kqkacP1UiqS7nvKt7QqE8tU45M98d6kX6CKfRY=; b=daL/rTGjvdGmdBbtweeVRJCfChFOeyASFhiNeggPnBagKi6XBov6XcUGvq8F1EZh75 l4MU5NZnkastiqNR2qcplcHvxNX2OLGEBmoFZqX50lKXclkrCq114LjenJG/bRoJY03O BCT/c42B9AhRlGpYlqrphm9tptnhgbOlF/clccHZAzMkhRtG4hnJcTZufzXDPRH1s190 2bDmRpYWvbKvJViK+OmbktZxtyZqn5+EjLFapQT75hvuaQ09ssIonkf3FokYs6QHUspu DJeLXbIbbe0kj/yK7Ftc5x4J+6+TuMRxwcSLI9ufBlMHbI9vFhnTV7t2D0ItHiNUeenj FdSQ== X-Gm-Message-State: AOAM530LnxH/uxa3TV8J7x990Up27Tlyak0FIGITo+C0PUgvOClQieZK A3+L82LnJDaZpxaMAcsZuXLIWfrdKxakV7D8+bFY1C1/c3gBp/bWyabkY4yu0b0YlTQmFvJodkh Tp53W0QovAvZpoRIu X-Received: by 2002:aa7:c403:: with SMTP id j3mr2619821edq.217.1606824457752; Tue, 01 Dec 2020 04:07:37 -0800 (PST) X-Google-Smtp-Source: ABdhPJx1DxtyPC6a1zqrYWrdj42DEWp1B5nUpOxzqYzTrKSPNVvFKMo0ahsqcxwarIESgnaxjNMXjQ== X-Received: by 2002:aa7:c403:: with SMTP id j3mr2619797edq.217.1606824457604; Tue, 01 Dec 2020 04:07:37 -0800 (PST) Received: from ?IPv6:2001:b07:6468:f312:c8dd:75d4:99ab:290a? ([2001:b07:6468:f312:c8dd:75d4:99ab:290a]) by smtp.gmail.com with ESMTPSA id u19sm750026ejg.16.2020.12.01.04.07.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 01 Dec 2020 04:07:36 -0800 (PST) To: Greg Kroah-Hartman Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org, David Woodhouse , Nikos Tsironis References: <20201201084647.751612010@linuxfoundation.org> <20201201084648.690944071@linuxfoundation.org> From: Paolo Bonzini Subject: Re: [PATCH 4.19 08/57] KVM: x86: Fix split-irqchip vs interrupt injection window request Message-ID: <41931e4a-45a5-5ef2-317d-a2a5ae649357@redhat.com> Date: Tue, 1 Dec 2020 13:07:36 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On 01/12/20 12:13, Greg Kroah-Hartman wrote: > If you look at the section onhttps://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html > that starts with "Additionally, some patches..." it will show that you > can add "#" comments on the cc: stable line to let me know pre-requsite > commits if you know them, and want to do that in the future. Yeah, I guess that one applies even if it was submitted in the same pull request. I have used it in the past but not for patches that were submitted in the same pull request, so in this case I should have marked patch 2 like this: Cc: stable@vger.kernel.org # 4.4.x: 123456: kvm: patch 1 in the series Cc: stable@vger.kernel.org # 4.4.x instead of marking both patches with just "Cc: stable". Upstream commit fcb3a1ab79904d54499db77017793ccca665eb7e is one case in which Rafael did this. Paolo