From: Antony Pavlov <antonynpavlov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Update/include some functions from the Kernel
Date: Tue, 15 Jul 2014 22:42:19 +0400 [thread overview]
Message-ID: <20140715224219.19f604e6d856a3aff702f702@gmail.com> (raw)
In-Reply-To: <1405432173-22448-1-git-send-email-s.hauer@pengutronix.de>
On Tue, 15 Jul 2014 15:49:28 +0200
Sascha Hauer <s.hauer@pengutronix.de> wrote:
After rebasing over latest next I have got many warnings like this:
CC common/filetype.o
In file included from include/common.h:26:0,
from common/filetype.c:18:
include/linux/bitops.h: In function 'hweight_long':
include/linux/bitops.h:77:2: warning: implicit declaration of function 'hweight32' [-Wimplicit-function-declaration]
return sizeof(w) == 4 ? hweight32(w) : hweight64(w);
^
include/linux/bitops.h:77:2: warning: implicit declaration of function 'hweight64' [-Wimplicit-function-declaration]
include/linux/bitops.h: In function 'fls_long':
include/linux/bitops.h:175:2: warning: implicit declaration of function 'fls64' [-Wimplicit-function-declaration]
return fls64(l);
^
> This adds/updates some lowlevel bitmap/bitop stuff from the
> Kernel. Needed by upcoming USB updates.
>
> Sascha
>
> ----------------------------------------------------------------
> Sascha Hauer (5):
> include: Add DECLARE_BITMAP from kernel
> include: Add round_up/round_down macros from kernel
> include: Add foreign endianess adding functions from kernel
> lib: Add bitmap functions from kernel
> include: update bitop functions from kernel
>
> include/asm-generic/bitops/hweight.h | 15 +
> include/linux/bitmap.h | 285 ++++++++++++
> include/linux/bitops.h | 214 ++++++++-
> include/linux/byteorder/generic.h | 29 ++
> include/linux/kernel.h | 13 +
> include/linux/types.h | 3 +
> lib/Makefile | 1 +
> lib/bitmap.c | 839 +++++++++++++++++++++++++++++++++++
> 8 files changed, 1398 insertions(+), 1 deletion(-)
> create mode 100644 include/linux/bitmap.h
> create mode 100644 lib/bitmap.c
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
--
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-07-15 18:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 13:49 Update/include some functions from the Kernel Sascha Hauer
2014-07-15 13:49 ` [PATCH 1/5] include: Add DECLARE_BITMAP from kernel Sascha Hauer
2014-07-15 13:49 ` [PATCH 2/5] include: Add round_up/round_down macros " Sascha Hauer
2014-07-15 13:49 ` [PATCH 3/5] include: Add foreign endianess adding functions " Sascha Hauer
2014-07-15 13:49 ` [PATCH 4/5] lib: Add bitmap " Sascha Hauer
2014-07-15 13:49 ` [PATCH 5/5] include: update bitop " Sascha Hauer
2014-07-15 18:42 ` Antony Pavlov [this message]
2014-07-16 8:27 ` Update/include some functions from the Kernel Sascha Hauer
2014-07-16 23:15 ` Sebastian Hesselbarth
2014-07-17 5:33 ` Sascha Hauer
2014-07-17 9:29 ` Sebastian Hesselbarth
2014-07-17 12:41 ` Sascha Hauer
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=20140715224219.19f604e6d856a3aff702f702@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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.