From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1764552AbdEXMLZ (ORCPT <rfc822;w@1wt.eu>);
        Wed, 24 May 2017 08:11:25 -0400
Received: from mga05.intel.com ([192.55.52.43]:6692 "EHLO mga05.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1764423AbdEXMLY (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 24 May 2017 08:11:24 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.38,386,1491289200"; 
   d="scan'208";a="1134241112"
Message-ID: <1495627881.6967.99.camel@linux.intel.com>
Subject: bitmap API consistency
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Martin Schwidefsky <schwidefsky@de.ibm.com>
Date: Wed, 24 May 2017 15:11:21 +0300
Organization: Intel Finland Oy
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.22.6-1 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi!

Surprisingly discovered today that bitmap API is not consistent in some
cases (at least one I found recently).

bitmap_fill() sets area of bits in a bitmap.
bitmap_zero() clears them.

However, if _fill() does something sane, _zero() clears _all_ bits up to
word size (long).

I think it should be fixed to be consistent with _fill() variant.

Thoughts?

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy