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 1015EC433F5 for ; Wed, 22 Dec 2021 10:43:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234734AbhLVKnS (ORCPT ); Wed, 22 Dec 2021 05:43:18 -0500 Received: from dfw.source.kernel.org ([139.178.84.217]:42824 "EHLO dfw.source.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236501AbhLVKnS (ORCPT ); Wed, 22 Dec 2021 05:43:18 -0500 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id A655861968; Wed, 22 Dec 2021 10:43:17 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 99192C36AE8; Wed, 22 Dec 2021 10:43:15 +0000 (UTC) Date: Wed, 22 Dec 2021 10:43:12 +0000 From: Catalin Marinas To: Christoph Hellwig Cc: Xiongfeng Wang , will@kernel.org, mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, moyufeng@huawei.com, linux-arch@vger.kernel.org Subject: Re: [PATCH] asm-generic: introduce io_stop_wc() and add implementation for ARM64 Message-ID: References: <20211217085611.111999-1-wangxiongfeng2@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-arch@vger.kernel.org On Wed, Dec 22, 2021 at 01:08:15AM -0800, Christoph Hellwig wrote: > So what is going to use this? There was a series about 6 months ago making use of the new DGH arm64 instruction in a network driver: https://lore.kernel.org/r/1627614864-50824-1-git-send-email-huangguangbin2@huawei.com We bike-shedded on the name of the macro since (now settled on io_stop_wc()) and there wasn't much point in carrying the rest of the patches. I assume the driver changes will go in via their normal route once the macro above is merged. -- Catalin