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 us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (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 E7615C433EF for ; Mon, 7 Mar 2022 16:48:29 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-45-PIDWUbp4PGWmHOS-715H1A-1; Mon, 07 Mar 2022 11:48:24 -0500 X-MC-Unique: PIDWUbp4PGWmHOS-715H1A-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 6717D3C17B43; Mon, 7 Mar 2022 16:48:22 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id 52C9C1466C41; Mon, 7 Mar 2022 16:48:22 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 0D00A19305AB; Mon, 7 Mar 2022 16:48:22 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 7BF3719305AA for ; Mon, 7 Mar 2022 16:48:21 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 683CF400E87F; Mon, 7 Mar 2022 16:48:21 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast08.extmail.prod.ext.rdu2.redhat.com [10.11.55.24]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 646F440E043C for ; Mon, 7 Mar 2022 16:48:21 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [205.139.110.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 2234C3803905 for ; Mon, 7 Mar 2022 16:48:21 +0000 (UTC) Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-122-GY0QnJqxNLWtIXpinakwjA-1; Mon, 07 Mar 2022 11:48:18 -0500 X-MC-Unique: GY0QnJqxNLWtIXpinakwjA-1 Received: by verein.lst.de (Postfix, from userid 2407) id 27E0868AFE; Mon, 7 Mar 2022 17:48:15 +0100 (CET) Date: Mon, 7 Mar 2022 17:48:14 +0100 From: Christoph Hellwig To: Mike Snitzer Message-ID: <20220307164814.GA12591@lst.de> References: <20220304180105.409765-1-hch@lst.de> <164666057398.15541.7415780807920631127.b4-ty@kernel.dk> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-Mimecast-Impersonation-Protect: Policy=CLT - Impersonation Protection Definition; Similar Internal Domain=false; Similar Monitored External Domain=false; Custom External Domain=false; Mimecast External Domain=false; Newly Observed Domain=false; Internal User Name=false; Custom Display Name List=false; Reply-to Address Mismatch=false; Targeted Threat Dictionary=false; Mimecast Threat Dictionary=false; Custom Threat Dictionary=false X-Scanned-By: MIMEDefang 2.84 on 10.11.54.1 Subject: Re: [dm-devel] remove bio_devname X-BeenThere: dm-devel@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: device-mapper development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Jens Axboe , linux-raid@vger.kernel.org, Theodore Ts'o , linux-block@vger.kernel.org, Song Liu , dm-devel@redhat.com, linux-ext4@vger.kernel.org, Christoph Hellwig Errors-To: dm-devel-bounces@redhat.com Sender: "dm-devel" X-Scanned-By: MIMEDefang 2.85 on 10.11.54.7 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dm-devel-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Mon, Mar 07, 2022 at 11:45:53AM -0500, Mike Snitzer wrote: > Should those go through block too? Or is there no plan to remove > bdevname()? My preference would be: do the full bio_devname removal through Jens' tree and you keep the bvdevname removal. I hope bdevname will go away as well, but certainly not in this merge window. -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel 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 E61F9C433F5 for ; Mon, 7 Mar 2022 16:48:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236982AbiCGQtP (ORCPT ); Mon, 7 Mar 2022 11:49:15 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40756 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237206AbiCGQtN (ORCPT ); Mon, 7 Mar 2022 11:49:13 -0500 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2D3DD22523; Mon, 7 Mar 2022 08:48:19 -0800 (PST) Received: by verein.lst.de (Postfix, from userid 2407) id 27E0868AFE; Mon, 7 Mar 2022 17:48:15 +0100 (CET) Date: Mon, 7 Mar 2022 17:48:14 +0100 From: Christoph Hellwig To: Mike Snitzer Cc: Jens Axboe , Christoph Hellwig , dm-devel@redhat.com, linux-block@vger.kernel.org, linux-ext4@vger.kernel.org, linux-raid@vger.kernel.org, Theodore Ts'o , Song Liu Subject: Re: remove bio_devname Message-ID: <20220307164814.GA12591@lst.de> References: <20220304180105.409765-1-hch@lst.de> <164666057398.15541.7415780807920631127.b4-ty@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On Mon, Mar 07, 2022 at 11:45:53AM -0500, Mike Snitzer wrote: > Should those go through block too? Or is there no plan to remove > bdevname()? My preference would be: do the full bio_devname removal through Jens' tree and you keep the bvdevname removal. I hope bdevname will go away as well, but certainly not in this merge window.