Received: by 2002:a05:6358:c692:b0:131:369:b2a3 with SMTP id fe18csp799758rwb; Wed, 26 Jul 2023 03:07:43 -0700 (PDT) X-Google-Smtp-Source: APBJJlFCbWPPUYPVNZ6i1bGsh+nIxbmMhA+o+8/45j5BHp4Ud0eP4bKv7cPZJaprIM+niTfLWGf9 X-Received: by 2002:a17:903:1cf:b0:1b8:6a09:9cf9 with SMTP id e15-20020a17090301cf00b001b86a099cf9mr1573888plh.26.1690366063377; Wed, 26 Jul 2023 03:07:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1690366063; cv=none; d=google.com; s=arc-20160816; b=SEYy+2ErIW0AtCt3gPJF/NP1QzA2Be0QMhJF5hLZ6q0ELIKZp8BdgC0NtUNp/BN1ND wltJVxMkoq0X/7VkwdOLj/apuwnUJUPcn7C7weOESLUuCQupxvuUGg3XdojksrY2KK8r 6SY2WS3vH7UjeluC/JyL87eJUCOGubz8y5ZB+dfu686/6BDpIZIJu2AUotpcxlikQGpX QzaVq0JKninRXZA30O1CNvdAPf8YuNqzKcksyoqdUTiEqHqoSFuzOa4SWjvWKM4Fhh+6 IE6NGFoZaHztdyItpkRlf6XBUAZWGmsX+0eFA2hHeZwUAt6HGYMgqNOTBOSq/TMuWw3/ vPww== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=ABzWPhZex5U17USjXh755cllj6dPS5Rtp7cQpTBErJg=; fh=LJge3h3VltDQUoynNwMobx6Z2UgpEXerDBwKVqM0xJg=; b=oMl0ygvg6VAR/aWylVcAs33DLW3Y8nfj/2xl9LFQK3NI5uuG85ZnTERJuXKP+cRIeN v/SV9uiifjU8Uhrl/6TJCflE+yo9ZSjptDLi7Mw1/OLWjIXEtMDcgWDMto+VHZ4hWplh rdtUiW1rF4Fb47MwSMDi5aQQtBvt4+zNQfETiZoflmQutPVZx8NwrYSjWyI4bkopFxRT kcpLvWwYrLhO/ON0JDpeEQ2yN8COQWSbVUfK4ApFi2wiVHzmS+C5iXUggoU7uLYf/Bte o9IaFUClfBtvnLB+UBT8rWkjCTl1eh94HCUTsjlFSOP3SvlnJZFeKE3O+kWbL/geprmW AMFg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id u5-20020a170902e5c500b001b9d95078d9si13523579plf.404.2023.07.26.03.07.29; Wed, 26 Jul 2023 03:07:43 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229936AbjGZJc0 (ORCPT + 99 others); Wed, 26 Jul 2023 05:32:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50808 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232913AbjGZJcF (ORCPT ); Wed, 26 Jul 2023 05:32:05 -0400 Received: from szxga08-in.huawei.com (szxga08-in.huawei.com [45.249.212.255]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5715A1BE8; Wed, 26 Jul 2023 02:31:02 -0700 (PDT) Received: from dggpemm500016.china.huawei.com (unknown [172.30.72.57]) by szxga08-in.huawei.com (SkyGuard) with ESMTP id 4R9pXH4mt8z1GDFR; Wed, 26 Jul 2023 17:30:07 +0800 (CST) Received: from [10.67.108.26] (10.67.108.26) by dggpemm500016.china.huawei.com (7.185.36.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Wed, 26 Jul 2023 17:31:00 +0800 Message-ID: <43731b35-c076-6d01-ad83-764fb2e9a8f0@huawei.com> Date: Wed, 26 Jul 2023 17:30:49 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 Subject: Re: [PATCH -next v8 0/2] support allocating crashkernel above 4G explicitly on riscv Content-Language: en-US To: Conor Dooley CC: Conor Dooley , , , , , , , , , , , , , , , References: <20230725214413.2488159-1-chenjiahao16@huawei.com> <20230725-judiciary-auction-ef50be622175@spud> <96245a6f-cff1-9f2a-1217-4109d9a19291@huawei.com> <20230726-affix-employed-319aada685e7@wendy> From: "chenjiahao (C)" In-Reply-To: <20230726-affix-employed-319aada685e7@wendy> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.67.108.26] X-ClientProxiedBy: dggems704-chm.china.huawei.com (10.3.19.181) To dggpemm500016.china.huawei.com (7.185.36.25) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-4.3 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2023/7/26 14:45, Conor Dooley wrote: > On Wed, Jul 26, 2023 at 10:20:00AM +0800, chenjiahao (C) wrote: >> On 2023/7/26 5:48, Conor Dooley wrote: >>> Hey, >>> >>> Your $subject says -next, but the patch failed to apply to >>> riscv/for-next. What was the base for this patchset? >>> >>> Thanks, >>> Conor. >> Hi, >> >> My patchset was tested on current linux-next HEAD >> (commit ID: 1e25dd777248, tag: next-20230725) and >> it seems all ok. >> Could you try applying with the base above, or >> is there any problem with that base? > There's some difference between linux-next and riscv/for-next that > prevents the patchwork automation from applying the patches. Oh, I see. There is definitely a difference, since linux-next applied a bugfix patch b690e266dae2 ("riscv: mm: fix truncation warning on RV32") recently, whereas riscv/for-next didn't. I have worked on a wrong base and thanks for reminding :) I will rebase onto riscv/for-next and post my v9 pathset soon, please check over there. Thanks, Jiahao