From: "Gix, Brian" <brian.gix@intel.com>
To: Cinaed Simson <cinaed.simson@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: RE: bug in mesh/net.c
Date: Wed, 28 Nov 2018 17:01:40 +0000 [thread overview]
Message-ID: <DEBB0CAA2616974FAE35E4B560B9A4375C139642@ORSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <5e734285-be09-bfef-6795-237a5ab0350a@GMail.COM>
Hi Cinead,
> -----Original Message-----
> owner@vger.kernel.org] On Behalf Of Cinaed Simson
> Sent: Monday, November 26, 2018 11:51 PM
> Subject: bug in mesh/net.c
>
>
> Line 3317 in net.c reads something like
>
> for(int i=0, ....
>
> which I had change to
>
> int i;
> for(i=0,...
Thank you for this report. If you would like your name in the change log, please submit this as a GIT Patch, and I will apply it directly. Otherwise, I will make sure it is fixed in the next set of patches that we push.
> in order to get the latest git version of bluez to compile.
>
> -- Cinaed
next prev parent reply other threads:[~2018-11-28 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 7:50 bug in mesh/net.c Cinaed Simson
2018-11-28 17:01 ` Gix, Brian [this message]
2018-11-29 21:51 ` Cinaed Simson
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=DEBB0CAA2616974FAE35E4B560B9A4375C139642@ORSMSX103.amr.corp.intel.com \
--to=brian.gix@intel.com \
--cc=cinaed.simson@gmail.com \
--cc=linux-bluetooth@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 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).