[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfH7ZOQDXv+uDpXv8d_KX23-MWnWeWwd7i3RDvhWu_HnQ@mail.gmail.com>
Date: Sat, 16 Jun 2018 21:42:52 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Yury Norov <ynorov@...iumnetworks.com>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
agk@...hat.com, Mike Snitzer <snitzer@...hat.com>,
dm-devel@...hat.com, shli@...nel.org, linux-raid@...r.kernel.org,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
linux-input <linux-input@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>
Subject: Re: [PATCH v2 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
On Sat, Jun 16, 2018 at 1:24 AM Yury Norov <ynorov@...iumnetworks.com> wrote:
> On Fri, Jun 15, 2018 at 04:20:15PM +0300, Andy Shevchenko wrote:
> > A lot of code become ugly because of open coding allocations for bitmaps.
> >
> > Introduce three helpers to allow users be more clear of intention
> > and keep their code neat.
>
> I like the idea. But in following patches you switch to new API only
> couple of drivers.
I have converted much more, indeed.
I published only for couple of drivers as an example. This is I
mentioned in cover letter.
> I think, it worth to switch more, especially core
> users to make new API visible for developers. Brief grepping for
> candidates showse only 17 suspected places:
Yes, but not in this series. Since it covers many subsystems and
drivers the applying that kind of series would take ages. That's why I
have decided to submit for one subsystem only.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists