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 3334CC83F01 for ; Sat, 26 Aug 2023 07:46:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231421AbjHZHpv (ORCPT ); Sat, 26 Aug 2023 03:45:51 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60274 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231896AbjHZHpp (ORCPT ); Sat, 26 Aug 2023 03:45:45 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 372B3AC for ; Sat, 26 Aug 2023 00:45:43 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id BFCC160AFA for ; Sat, 26 Aug 2023 07:45:42 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9C335C433C7; Sat, 26 Aug 2023 07:45:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1693035942; bh=jbRlaGZgeH/nIUB92IrBZ2CS9Rn4xUf81ltVeKgCTS0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=tOmOTOehfejMw6TmNeJ0go3TdvMF1LuCEe4T8izxS2NEhgWma/BTBW+qc0da+Fcm6 /1KSQMi6Mdt6/6j60RNIXcEOcypFugr/KwhKn/RDzRgJdv7uTrsz6VfOQ9BAwIaDh9 5z1uBU2iM9LHkw/fb6PPjAKvpTB4ReWzhWZUvFgE= Date: Sat, 26 Aug 2023 09:45:39 +0200 From: Greg Kroah-Hartman To: Stanislav Kinsburskii Cc: Stanislav Kinsburskii , Derek Kiernan , Dragan Cvetic , Arnd Bergmann , Wei Liu , "K. Y. Srinivasan" , Madhavan Venkataraman , Anthony Yznaga , "Mike Rapoport (IBM)" , James Gowans , Anirudh Rayabharam , Jinank Jain , Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH] Introduce persistent memory pool Message-ID: <2023082633-magnetize-cupcake-accc@gregkh> References: <64e7cbf7.050a0220.114c7.b70dSMTPIN_ADDED_BROKEN@mx.google.com> <2023082506-enchanted-tripping-d1d5@gregkh> <64e8f6dd.050a0220.edb3c.c045SMTPIN_ADDED_BROKEN@mx.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <64e8f6dd.050a0220.edb3c.c045SMTPIN_ADDED_BROKEN@mx.google.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 22, 2023 at 06:36:10PM -0700, Stanislav Kinsburskii wrote: > > > +#include > > > +#include > > > +#include > > > +#include > > > + > > > +#include > > > + > > > +#define VERSION 1 > > > > In kernel code does not need versions. > > > > Could you elaborate on this? Should kernel version be used as a backward > compatitbility marker instead? kernel versions should never be checked for in-kernel code, so I really don't understand the question here sorry. For code that is in the kernel tree, having "versions" on them (as many drivers used to, and now only a few do), makes no sense, especially with the stable/lts trees getting fixes for them over time as well. In short, there should not be a need for a "version" anywhere. thanks, greg k-h