archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <>
To: Naresh Kamboju <>
Cc: Sasha Levin <>,
	linux- stable <>,,
	Andy Shevchenko <>,
	Dmitry Torokhov <>
Subject: Re: stable-rc 4.9.212-rc1/2e383da55e49: regressions detected in project stable v4.9.y on OE
Date: Tue, 28 Jan 2020 12:54:46 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Jan 28, 2020 at 05:14:33PM +0530, Naresh Kamboju wrote:
> stable-rc 4.9 build failed due to these build error,
> drivers/md/bitmap.c:1702:13: error: conflicting types for 'bitmap_free'
>  static void bitmap_free(struct bitmap *bitmap)
>              ^~~~~~~~~~~
> include/linux/bitmap.h:94:13: note: previous declaration of
> 'bitmap_free' was here
>  extern void bitmap_free(const unsigned long *bitmap);
>              ^~~~~~~~~~~
> scripts/ recipe for target 'drivers/md/bitmap.o' failed
> suspecting this patch causing this build failure on stable-rc 4.9
> bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
> commit c42b65e363ce97a828f81b59033c3558f8fa7f70 upstream.
> 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.
> Note, due to multiple circular dependencies we may not provide
> the helpers as inliners. For now we keep them exported and, perhaps,
> at some point in the future we will sort out header inclusion and
> inheritance.
> Signed-off-by: Andy Shevchenko <>
> Signed-off-by: Dmitry Torokhov <>
> Signed-off-by: Greg Kroah-Hartman <>

Sorry, my fault, am fixing this up for 4.9 and 4.4 and 4.14 right now...
Will push out new -rcs when working again.

greg k-h

  reply	other threads:[~2020-01-28 11:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28 11:44 stable-rc 4.9.212-rc1/2e383da55e49: regressions detected in project stable v4.9.y on OE Naresh Kamboju
2020-01-28 11:54 ` Greg Kroah-Hartman [this message]
2020-01-28 12:47   ` Greg Kroah-Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).