From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Sasha Levin <sashal@kernel.org>,
linux- stable <stable@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: stable-rc 4.9.212-rc1/2e383da55e49: regressions detected in project stable v4.9.y on OE
Date: Tue, 28 Jan 2020 13:47:49 +0100 [thread overview]
Message-ID: <20200128124749.GA2813069@kroah.com> (raw)
In-Reply-To: <20200128115446.GA2680602@kroah.com>
On Tue, Jan 28, 2020 at 12:54:46PM +0100, Greg Kroah-Hartman wrote:
> 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/Makefile.build:304: 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 <andriy.shevchenko@linux.intel.com>
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> 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.
Ok, should be now resolved, sorry for the mess.
greg k-h
prev parent reply other threads:[~2020-01-28 12:47 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
2020-01-28 12:47 ` Greg Kroah-Hartman [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200128124749.GA2813069@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.