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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6FCB6C41513 for ; Mon, 14 Aug 2023 23:17:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233443AbjHNXRV (ORCPT ); Mon, 14 Aug 2023 19:17:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39606 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233471AbjHNXQ5 (ORCPT ); Mon, 14 Aug 2023 19:16:57 -0400 Received: from mail-yw1-x1149.google.com (mail-yw1-x1149.google.com [IPv6:2607:f8b0:4864:20::1149]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1B63610F7 for ; Mon, 14 Aug 2023 16:16:56 -0700 (PDT) Received: by mail-yw1-x1149.google.com with SMTP id 00721157ae682-589cd098d24so44906887b3.0 for ; Mon, 14 Aug 2023 16:16:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1692055015; x=1692659815; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=XJ2VqA/vSflBac203Z0ZgYzciS8CSN/YrZrCQZvgAqE=; b=OxYYoyUAQaeaCm0MRnDlT6YpDWZ0eDciFaHbssoRAoYyzjd2o0WDI1UOBCOxL+kMJc 5YD0NK8r1uDf6e0Jatvt+d6P+BWzIhvUYoQQhLjByYnja3UBlbXrGoFe9hBNCSmd3Por 77GbZptlqN3qID9Yi7OuuYNKro+YD6l9Q6jj3+sUYzoK08H9wS69cXzUBziAMKx3xld/ w96wxOhnL73JzIXq2lGp1mV73XNcE7Ps2NUvuAohRziILKeBly43Y5qUc7dLaviqameq hE+kTcQyTkgYI/ntVGdkCqeR0EWDhGYDk0kgtw+nvGshr7JSpUCtOXj/qFAa5uoFZbVm YkSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692055015; x=1692659815; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=XJ2VqA/vSflBac203Z0ZgYzciS8CSN/YrZrCQZvgAqE=; b=eHbvxykDZlIwRdS9+N9QtUfcXSEaNew0aexJPBekqTShdNkoYeUVW8f41ddQv+jmWx 7hh+lcNdhLoK/GC2Pm+7/4kDBYiqlidgb+H0zDY0pbCIi49+PrC2TKibZNOmFeGF/eBb DuOdNTgjzB8+s9u2yIRr9t+e1Sd5bhQwv+j3fvR9l1eI3od6EsLLd/9mtYlvbEueh2EL l3fhYYkVDewmWb9/Di7ih2rPAKEEYgyKZbAdqktCWsk5hi5jDpo/gWdBBhhIdxWXExeM sgJAkExnpsm4DohVwViiAE00TlgA+63rcBafSchNaatFFKV7NbtxLTq7Ub0B4vuFN3d4 ByKQ== X-Gm-Message-State: AOJu0Yx7aSbl4acutkw9kA5LyqvAE7B74YPUBeDCQ3pJRPg/8mSGx865 j9f12wO6eTM49SMbFZFTQmjhYzONLmY= X-Google-Smtp-Source: AGHT+IGO0AL45xRymm0BjDJln3deMA/9LFqjImi7JInSUnl69k7Qer+RG4sudzofLCbCQa+Rdgz1TuaGB1A= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a05:690c:709:b0:57a:118a:f31 with SMTP id bs9-20020a05690c070900b0057a118a0f31mr180335ywb.7.1692055015309; Mon, 14 Aug 2023 16:16:55 -0700 (PDT) Date: Mon, 14 Aug 2023 16:16:53 -0700 In-Reply-To: <20230811045127.3308641-1-rananta@google.com> Mime-Version: 1.0 References: <20230811045127.3308641-1-rananta@google.com> Message-ID: Subject: Re: [PATCH v9 00/14] KVM: arm64: Add support for FEAT_TLBIRANGE From: Sean Christopherson To: Raghavendra Rao Ananta Cc: Oliver Upton , Marc Zyngier , James Morse , Suzuki K Poulose , Paolo Bonzini , Huacai Chen , Zenghui Yu , Anup Patel , Atish Patra , Jing Zhang , Reiji Watanabe , Colton Lewis , David Matlack , Fuad Tabba , linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, linux-mips@vger.kernel.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 11, 2023, Raghavendra Rao Ananta wrote: > The series is based off of upstream v6.5-rc1. Lies! :-) This is based off one of the kvmarm.git topic branches (I didn't bother to figure out which one), not v6.5-rc1. Please try to incorporate git format-patch's "--base" option into your workflow, e.g. I do "git format-patch --base=HEAD~$nr" where $nr is the number of patches I am posting. It's not foolproof, e.g. my approach doesn't help if I have a local patch that I'm not posting, but 99% of the time it Just Works and eliminates any ambuitity. You can also do "--base=auto", but that only does the right thing if your series has its upstream branch set to the base/tree that you want your patches applied to (I use the upstream branch for a completely different purpose for my dev branches).