From: Johan Hedberg <johan.hedberg@gmail.com>
To: Mikel Astiz <mikel.astiz.oss@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, Mikel Astiz <mikel.astiz@bmw-carit.de>
Subject: Re: [PATCH obexd v3 6/6] client: queue transfers in pbap sessions
Date: Fri, 17 Feb 2012 11:56:36 +0200 [thread overview]
Message-ID: <20120217095636.GC13492@x220> (raw)
In-Reply-To: <1329400834-8400-7-git-send-email-mikel.astiz.oss@gmail.com>
Hi Mikel,
On Thu, Feb 16, 2012, Mikel Astiz wrote:
> +struct pending_request *pending_request_new(struct pbap_data *pbap,
> + DBusMessage *message)
> +{
> + struct pending_request *p;
> +
> + p = g_new0(struct pending_request, 1);
> + p->pbap = pbap;
> + p->msg = dbus_message_ref(message);
> +
> + return p;
> +}
This will cause a compilation warning/error since you're not exporting
the function through any .h file. I suppose you intended to declare it
static? Also, this implies that you're not doing compilation tests with
./bootstrap-configure since it converts all warnings to errors and would
have made it impossible to compile the code. Please always use that when
writing new code.
Johan
prev parent reply other threads:[~2012-02-17 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 14:00 [PATCH obexd v3 0/6] Several minor fixes Mikel Astiz
2012-02-16 14:00 ` [PATCH obexd v3 1/6] client: fix memory leak in obc_session_put Mikel Astiz
2012-02-16 14:00 ` [PATCH obexd v3 2/6] client: fix unreported error case Mikel Astiz
2012-02-17 9:51 ` Johan Hedberg
2012-02-16 14:00 ` [PATCH obexd v3 3/6] client: fix incorrect error check Mikel Astiz
2012-02-17 9:54 ` Johan Hedberg
2012-02-16 14:00 ` [PATCH obexd v3 4/6] client: fix pbap select when same path given twice Mikel Astiz
2012-02-16 14:00 ` [PATCH obexd v3 5/6] client: queue transfers in ftp sessions Mikel Astiz
2012-02-16 14:00 ` [PATCH obexd v3 6/6] client: queue transfers in pbap sessions Mikel Astiz
2012-02-17 9:56 ` Johan Hedberg [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=20120217095636.GC13492@x220 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mikel.astiz.oss@gmail.com \
--cc=mikel.astiz@bmw-carit.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 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).