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 66E68C433F5 for ; Wed, 24 Nov 2021 03:48:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240879AbhKXDvM (ORCPT ); Tue, 23 Nov 2021 22:51:12 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47776 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240875AbhKXDvM (ORCPT ); Tue, 23 Nov 2021 22:51:12 -0500 Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 595EDC061714 for ; Tue, 23 Nov 2021 19:48:03 -0800 (PST) Received: by mail-pj1-x102f.google.com with SMTP id np6-20020a17090b4c4600b001a90b011e06so1319435pjb.5 for ; Tue, 23 Nov 2021 19:48:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BQpMJpPq/OIJ1A+jReESOD3pvkOjXmQh8KJADyXTrz8=; b=jKMXPC6R380cNIQ/lk6QhOIiLqsp4XKj1eRLbWdIfXDMXjf2sFtM/A4DNKzZle92lO 3U1GnSeEGBEEzHeeSOTcj6e6Hlhrl2Cgom3C+oy6m84LroLIm83mhibtNhOC9a7kpuLa ouXLOQwDClItscEUt0Jtcfsiacpxarhj3trqquFBkBV1VRiZIUVoCcdmCugOwJ+8mJs6 RFqDPmjgXZyOm3EQaprR9sZoOXJ0YQXXHWkXXD+DsFaSM6qnnUL3vYnF49/xzscWLZfD M7pqOQ9uH/J1/XHGYxb48lxo0PQegLqWhqBsHyRYBVi7oUWjdYWmqFepS80LAFQdqtcA s5yA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BQpMJpPq/OIJ1A+jReESOD3pvkOjXmQh8KJADyXTrz8=; b=Zblkgli7F4HohmNPVnBh3neUTv/cX/88I9tecd4uUqSzMO5yn9fvhtKgY8XIRicUxp Wt7L15IvPVgwyr8LEkVoeubKjX+jqS7cYfk6KWdCkKpmgkWUVYByPsvEOyIkzXO9TvpO ONDSdVYIOo9pS93WSRtj8ibZ167e37u3BqZPNB6qqp8YFLod19Vs7gbXTGRwCd5yeni0 +uQWz+NfMyafFfOPkKgWTQ0Qcaw5yfvU4m8NCaIaYe1rsO8cQ0UoXnbHDbouU/VAHuoZ GMSRuot0bCBY9odtuVKKrlbe5ZPfyPfcz5FZZrrEdWTlPjnBgduAZGMZ2K9z/GO9egJJ J0fQ== X-Gm-Message-State: AOAM530Dhd3/6Me6MEL8CZZaSM1Z51ETOHdH1CbouD4CSEIWv280yuo6 PT6sIF80hdHhRlAGDoo3afMt2aKZ2xOZN2npmUgCOQ== X-Google-Smtp-Source: ABdhPJwXdBqxRTwwq0bi38HdemI3/UrUSQvkef2geUCQrgUs13GwLl6CkzHERiNWivJH+HCOX6YcKKMcXBwB2wDg59I= X-Received: by 2002:a17:902:6acb:b0:142:76c3:d35f with SMTP id i11-20020a1709026acb00b0014276c3d35fmr13991510plt.89.1637725682824; Tue, 23 Nov 2021 19:48:02 -0800 (PST) MIME-Version: 1.0 References: <20211109083309.584081-1-hch@lst.de> <20211109083309.584081-28-hch@lst.de> In-Reply-To: <20211109083309.584081-28-hch@lst.de> From: Dan Williams Date: Tue, 23 Nov 2021 19:47:52 -0800 Message-ID: Subject: Re: [PATCH 27/29] dax: fix up some of the block device related ifdefs To: Christoph Hellwig Cc: Mike Snitzer , Ira Weiny , device-mapper development , linux-xfs , Linux NVDIMM , linux-s390 , linux-fsdevel , linux-erofs@lists.ozlabs.org, linux-ext4 , virtualization@lists.linux-foundation.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org On Tue, Nov 9, 2021 at 12:34 AM Christoph Hellwig wrote: > > The DAX device <-> block device association is only enabled if > CONFIG_BLOCK is enabled. Update dax.h to account for that and use > the right conditions for the fs_put_dax stub as well. Looks good to me. Reviewed-by: Dan Williams > > Signed-off-by: Christoph Hellwig