[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2023082633-magnetize-cupcake-accc@gregkh>
Date: Sat, 26 Aug 2023 09:45:39 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Stanislav Kinsburskii <skinsburskii@...ux.microsoft.com>
Cc: Stanislav Kinsburskii <stanislav.kinsburskii@...il.com>,
Derek Kiernan <derek.kiernan@....com>,
Dragan Cvetic <dragan.cvetic@....com>,
Arnd Bergmann <arnd@...db.de>, Wei Liu <wei.liu@...nel.org>,
"K. Y. Srinivasan" <kys@...rosoft.com>,
Madhavan Venkataraman <madvenka@...ux.microsoft.com>,
Anthony Yznaga <anthony.yznaga@...cle.com>,
"Mike Rapoport (IBM)" <rppt@...nel.org>,
James Gowans <jgowans@...zon.com>,
Anirudh Rayabharam <anrayabh@...ux.microsoft.com>,
Jinank Jain <jinankjain@...ux.microsoft.com>,
Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] Introduce persistent memory pool
On Tue, Aug 22, 2023 at 06:36:10PM -0700, Stanislav Kinsburskii wrote:
> > > +#include <linux/bitmap.h>
> > > +#include <linux/memblock.h>
> > > +#include <linux/spinlock.h>
> > > +#include <linux/types.h>
> > > +
> > > +#include <linux/pmpool.h>
> > > +
> > > +#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
Powered by blists - more mailing lists