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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 89F80C433EF for ; Mon, 18 Oct 2021 15:22:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6F7AA60EE2 for ; Mon, 18 Oct 2021 15:22:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233219AbhJRPYm (ORCPT ); Mon, 18 Oct 2021 11:24:42 -0400 Received: from verein.lst.de ([213.95.11.211]:34796 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232844AbhJRPYh (ORCPT ); Mon, 18 Oct 2021 11:24:37 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id A661268AFE; Mon, 18 Oct 2021 17:22:24 +0200 (CEST) Date: Mon, 18 Oct 2021 17:22:24 +0200 From: Christoph Hellwig To: Coly Li Cc: Arnd Bergmann , Arnd Bergmann , Jens Axboe , Kent Overstreet , Linux Kernel Mailing List , Christoph Hellwig Subject: Re: [PATCH] [v2] bcache: hide variable-sized types from uapi header check Message-ID: <20211018152224.GB31195@lst.de> References: <20210928085554.2299495-1-arnd@kernel.org> <12a593bc-68bc-ac03-0307-a65a0c064af3@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <12a593bc-68bc-ac03-0307-a65a0c064af3@suse.de> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 18, 2021 at 10:42:37PM +0800, Coly Li wrote: > I am quite open for this idea. It is in uapi directory before I maintain > bcache. I just though the header fines on-media format should go into > include/uapi/, but if this is not the restricted rule, it is fine for me to > move this header to drivers/md/bcache/. Treating the on-disk definitions as a UAPI doesn't make much sense to me. I like keeping it in a separate header to make clear what is the on-disk format and what is just in core, but it should normally live with the rest of the code.