From: Gustavo F. Padovan <gustavo@padovan.org>
To: ofono@ofono.org
Subject: Re: [PATCH 2/5] Move bluetooth utils from hfp.c to bluetooth.c
Date: Sat, 12 Jun 2010 02:13:54 -0300 [thread overview]
Message-ID: <20100612051354.GB32159@vigoh> (raw)
In-Reply-To: <201006112309.55839.denkenz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
Hi Denis,
* Denis Kenzior <denkenz@gmail.com> [2010-06-11 23:09:55 -0500]:
> Hi Gustavo,
> > > So this should be in a separate patch...
> >
> > If I put this in a separate patch, it won't compile because no one is
> > using send_method_call_with_reply.
>
> Its ok, I just want to be able to follow the patches. Breaking them up will
> be much easier on me.
Ok, but we are breaking bisect this way.
--
Gustavo F. Padovan
http://padovan.org
next prev parent reply other threads:[~2010-06-12 5:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 7:43 [PATCH 1/5] Add bluetooth plugin skeleton Gustavo F. Padovan
2010-06-08 7:43 ` [PATCH 2/5] Move bluetooth utils from hfp.c to bluetooth.c Gustavo F. Padovan
2010-06-08 7:43 ` [PATCH 3/5] Remove send_method_call from hfp.c Gustavo F. Padovan
2010-06-08 7:43 ` [PATCH 4/5] Move create_path() to bluetooth plugin Gustavo F. Padovan
2010-06-08 7:44 ` [PATCH 5/5] Remove hfpmodem's header guard Gustavo F. Padovan
2010-06-10 21:19 ` Denis Kenzior
2010-06-10 21:17 ` [PATCH 2/5] Move bluetooth utils from hfp.c to bluetooth.c Denis Kenzior
2010-06-12 3:53 ` Gustavo F. Padovan
2010-06-12 4:09 ` Denis Kenzior
2010-06-12 5:13 ` Gustavo F. Padovan [this message]
2010-06-10 21:13 ` [PATCH 1/5] Add bluetooth plugin skeleton Denis Kenzior
-- strict thread matches above, loose matches on Subject: below --
2010-06-05 2:40 Gustavo F. Padovan
2010-06-05 2:40 ` [PATCH 2/5] Move bluetooth utils from hfp.c to bluetooth.c Gustavo F. Padovan
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=20100612051354.GB32159@vigoh \
--to=gustavo@padovan.org \
--cc=ofono@ofono.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.