Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <aae2f4c3dcd878adb30e8324ca8938de91b79241.camel@redhat.com>
Subject: Re: [PATCH 1/1] xarray: Document necessary flag in alloc-functions
From:   Philipp Stanner <pstanner@redhat.com>
To:     Matthew Wilcox <willy@infradead.org>
Cc:     linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Date:   Mon, 17 Jul 2023 10:59:32 +0200
In-Reply-To: <ZLDZnHY0af4bQqBw@casper.infradead.org>
References: <20230713161712.3163-1-pstanner@redhat.com>
         <ZLDZnHY0af4bQqBw@casper.infradead.org>
Organization: Red Hat Inc.
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Fri, 2023-07-14 at 06:14 +0100, Matthew Wilcox wrote:
> On Thu, Jul 13, 2023 at 06:17:11PM +0200, Philipp Stanner wrote:
> > I would pick up the other places where this information has to be
> > added if someone can provide me with a list :)
> 
> I'd suggest every wrapper function that calls __xa_alloc() or
> __xa_alloc_cyclic() needs this same information (I think you caught
> one of the six in the header file?).

Alright, got them. I'll send a follow-up.

But what do you think about __xa_alloc() and __xa_alloc_cyclic()
themselves? They are part of the advanced user API afaik.

P.