[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Yz7RCVTUeZAa4zM7@yury-laptop>
Date: Thu, 6 Oct 2022 05:58:49 -0700
From: Yury Norov <yury.norov@...il.com>
To: Valentin Schneider <vschneid@...hat.com>
Cc: linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
Jens Axboe <axboe@...nel.dk>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Juri Lelli <juri.lelli@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Steven Rostedt <rostedt@...dmis.org>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Daniel Bristot de Oliveira <bristot@...hat.com>
Subject: Re: [PATCH bitmap-for-next 0/5] bitmap,cpumask: Add
for_each_cpu_andnot()
On Mon, Oct 03, 2022 at 11:54:20AM -0700, Yury Norov wrote:
> On Mon, Oct 03, 2022 at 04:34:15PM +0100, Valentin Schneider wrote:
> > As suggested by Yury, this is the bitmap/cpumask specific bits of [1]. This now
> > also contains an extra fix for blk_mq.
>
> Patches ##2-5 look good to me, but I'd like to give them some testing.
> Let's also wait for other comments, and if nothing wrong will be spotted,
> I'll take it.
OK, taking those in bitmap-for-next.
Powered by blists - more mailing lists