From: Alexander Aring <alex.aring@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>,
linux-wpan@vger.kernel.org, kernel@pengutronix.de,
Jukka Rissanen <jukka.rissanen@linux.intel.com>,
Martin Townsend <mtownsend1973@gmail.com>,
Stefan Schmidt <s.schmidt@samsung.com>
Subject: Re: [PATCHv5 bluetooth-next 0/3] 6lowpan: introduce nhc framework
Date: Sat, 14 Feb 2015 22:57:27 +0100 [thread overview]
Message-ID: <20150214215724.GA18210@omega> (raw)
In-Reply-To: <777F808E-9C18-4C35-8C1C-4FD732F4FDC1@holtmann.org>
Hi Marcel,
On Sat, Feb 14, 2015 at 01:46:43PM -0800, Marcel Holtmann wrote:
...
>
> so I collected the reviewed-by and acked-by statements, but when I did a simple compile test it failed badly.
>
> CC net/6lowpan/nhc.o
> net/6lowpan/nhc.c: In function ‘lowpan_nhc_add’:
> net/6lowpan/nhc.c:206:2: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
> WARN_ONCE(nhc->idlen > LOWPAN_NHC_MAX_ID_LEN,
> ^
>
mhh, okay. Should be fixed with a conversion from "%d" -> "%zd". I will
resend a new series with this fix. Thanks.
- Alex
next prev parent reply other threads:[~2015-02-14 21:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 15:42 [PATCHv5 bluetooth-next 0/3] 6lowpan: introduce nhc framework Alexander Aring
2015-01-09 15:42 ` [PATCHv5 bluetooth-next 1/3] 6lowpan: add generic nhc layer interface Alexander Aring
2015-01-09 16:30 ` Stefan Schmidt
2015-01-09 15:42 ` [PATCHv5 bluetooth-next 2/3] 6lowpan: add udp compression via nhc layer Alexander Aring
2015-01-09 16:30 ` Stefan Schmidt
2015-01-09 15:42 ` [PATCHv5 bluetooth-next 3/3] 6lowpan: nhc: add other known rfc6282 compressions Alexander Aring
2015-01-09 16:30 ` Stefan Schmidt
2015-01-12 9:23 ` [PATCHv5 bluetooth-next 0/3] 6lowpan: introduce nhc framework Jukka Rissanen
2015-02-05 9:07 ` Alexander Aring
2015-02-14 21:33 ` Alexander Aring
2015-02-14 21:46 ` Marcel Holtmann
2015-02-14 21:57 ` Alexander Aring [this message]
2015-02-14 22:08 ` Marcel Holtmann
2015-02-14 22:10 ` Marcel Holtmann
2015-02-14 22:42 ` Alexander Aring
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=20150214215724.GA18210@omega \
--to=alex.aring@gmail.com \
--cc=jukka.rissanen@linux.intel.com \
--cc=kernel@pengutronix.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mtownsend1973@gmail.com \
--cc=s.schmidt@samsung.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox