[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZF0LXRWZb+xL+pTS@infradead.org>
Date: Thu, 11 May 2023 08:35:57 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Christian Göttsche <cgzones@...glemail.com>
Cc: selinux@...r.kernel.org, Jens Axboe <axboe@...nel.dk>,
Alistair Delva <adelva@...gle.com>,
Bart Van Assche <bvanassche@....org>,
Serge Hallyn <serge@...lyn.com>, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: [PATCH v4 4/9] block: use new capable_any functionality
On Thu, May 11, 2023 at 04:25:27PM +0200, Christian Göttsche wrote:
> Use the new added capable_any function in appropriate cases, where a
> task is required to have any of two capabilities.
What is this new function and why should we using it?
Your also forgot to Cc the block list on the entire series, making this
page completely unreviewable.
Powered by blists - more mailing lists