From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [45.249.212.190]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 456A717C2; Thu, 23 May 2024 01:42:59 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.249.212.190 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716428582; cv=none; b=YDNqWer5Z1y2N8BALvJCe1JlfuayY5rthOox/IZ/A4YF5+e/E+VygSq84hV4GBW77gyVU7d0P7IqUFQDmFQ70TPZ7Eo4lDZThEMzB549fhAZULIhJ7MsyK7bPicRUbKofaBnvFeOj3XFXCxQZYJL53Ks/s8xtEJ9vpEmdmUcNbY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716428582; c=relaxed/simple; bh=eeUvrJQaoEchYn+M2SIKzuf4GCNGNI557vCfeFKSwy4=; h=Message-ID:Date:MIME-Version:Subject:To:CC:References:From: In-Reply-To:Content-Type; b=HsSAjUxeZHM2pPpMjA1iTUAYMmwPqRtX7gh2PfNBNUN2kDX8yW32Dxc5DBBw98Pk8ChXK0r0H1aJLAwrLiSkdYoybutDUqlhdJJEnUD+ds4CbCsGw8xrs5TNEvhPEv3QPEqC8NPMw7NAvyvFUCivlB8ZS3NFAcLlw8keF+SviuY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=45.249.212.190 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.19.163.44]) by szxga04-in.huawei.com (SkyGuard) with ESMTP id 4Vl9np6vh4z2CjFs; Thu, 23 May 2024 09:39:26 +0800 (CST) Received: from kwepemf100007.china.huawei.com (unknown [7.202.181.221]) by mail.maildlp.com (Postfix) with ESMTPS id 7863D140153; Thu, 23 May 2024 09:42:56 +0800 (CST) Received: from [10.67.109.184] (10.67.109.184) by kwepemf100007.china.huawei.com (7.202.181.221) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.4; Thu, 23 May 2024 09:42:55 +0800 Message-ID: Date: Thu, 23 May 2024 09:42:54 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] riscv, bpf: Use STACK_ALIGN macro for size rounding up Content-Language: en-US To: Xiao Wang CC: , , , , , , , , , , , , , , , , , , , , , References: <20240522054507.3941595-1-xiao.w.wang@intel.com> From: Pu Lehui In-Reply-To: <20240522054507.3941595-1-xiao.w.wang@intel.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-ClientProxiedBy: dggems704-chm.china.huawei.com (10.3.19.181) To kwepemf100007.china.huawei.com (7.202.181.221) On 2024/5/22 13:45, Xiao Wang wrote: > Use the macro STACK_ALIGN that is defined in asm/processor.h for stack size > rounding up, just like bpf_jit_comp32.c does. > > Signed-off-by: Xiao Wang > --- > arch/riscv/net/bpf_jit_comp64.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) It met a patching conflict. I think you should target for the bpf-next tree. https://github.com/kernel-patches/bpf/pull/7080