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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1D474C32789 for ; Sun, 21 Aug 2022 06:58:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=MWc/fhr/PDPsiF7Sy5WorJC1ZKB/wv5Dnfl1+yvNrQg=; b=DcgbTQNPOSe69X 79Y3/Y5xhxDVRfhnlzVO3HmQh6p4BBbn9EDUCT9gToy9EGpCdCtA7P/SxHY3SWC2Ss5bijHNYq4D+ macBYwOyfsB080CPpimp4AoddRhQZC734B9XeCsTumNOhwe9OYkoB8QGFqxVEfiplipuAmfUNSyRS kIaV1nAuiuj9OTi0P0JGoNgbBnoyJKbQ0XuluePgUFqLm+NjswbjimlbzPsjDZybnA3BYMudwLPam 9ErRYwNoSBqoKP1Ahez6zzg1TAgHPdhvfqA8uTybT8jW+szGvkQ2JmkYfFzjCNVEUENtyNnHiK83F wg0r+v5EiXf3SIU17jWA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oPett-00722x-Ib; Sun, 21 Aug 2022 06:57:37 +0000 Received: from hch by bombadil.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1oPetl-0071xF-ID; Sun, 21 Aug 2022 06:57:30 +0000 Date: Sat, 20 Aug 2022 23:57:29 -0700 From: Christoph Hellwig To: Baoquan He Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, akpm@linux-foundation.org, hch@infradead.org, agordeev@linux.ibm.com, wangkefeng.wang@huawei.com, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2 03/11] mm: ioremap: allow ARCH to have its own ioremap definition Message-ID: References: <20220820003125.353570-1-bhe@redhat.com> <20220820003125.353570-4-bhe@redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20220820003125.353570-4-bhe@redhat.com> X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Sat, Aug 20, 2022 at 08:31:17AM +0800, Baoquan He wrote: > Architectures like xtensa, arc, can be converted to GENERIC_IOREMAP, > to take standard ioremap_prot() and ioremap_xxx() way. But they have > ARCH specific handling for ioremap() method, than standard ioremap() > method. Do they? For arc, the arc_uncached_addr_space case can be easily handled by arch_ioremap, and the xtensa case looks very similar to that. I'd really like to kill off arch definitions of ioremap going forward, as they should just be a special case of ioremap_prot by definition. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel