From: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>
To: Gustavo Padovan <gustavo@padovan.org>,
Mat Martineau <mathewm@codeaurora.org>,
linux-bluetooth@vger.kernel.org, pkrystad@codeaurora.org
Subject: Re: [PATCHv2 2/2] Bluetooth: Lock the L2CAP channel when sending
Date: Wed, 16 May 2012 17:50:39 +0300 [thread overview]
Message-ID: <20120516145037.GC10880@aemeltch-MOBL1> (raw)
In-Reply-To: <20120508074451.GA19057@joana>
Hi Gustavo,
On Tue, May 08, 2012 at 04:44:51AM -0300, Gustavo Padovan wrote:
> > > Patch has been applied to the bluetooth tree. Thanks.
> >
> > What about applying the first patch? I actually pulled that patch from
> > bluetooth-next and modified locking in my code but now that patch seems to
> > be lost.
>
> I applied it to bluetooth.git. Now you have to wait we merge bluetooth.git
> into bluetooth-next.git, that will happen shortly after John pull the pull
> request I sent.
What about the patch in question? Since it was in repository before I have
modified my code and changed locking logic but then patch disappeared.
Not that I think the patch is very important but I do not work to modify code too
often...
Best regards
Andrei Emeltchenko
next prev parent reply other threads:[~2012-05-16 14:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 21:20 [PATCHv2 0/2] Reworked send locking patches Mat Martineau
2012-05-04 21:20 ` [PATCHv2 1/2] Bluetooth: Restore locking semantics when looking up L2CAP channels Mat Martineau
2012-05-04 21:20 ` [PATCHv2 2/2] Bluetooth: Lock the L2CAP channel when sending Mat Martineau
2012-05-05 0:01 ` Gustavo Padovan
2012-05-08 7:42 ` Andrei Emeltchenko
2012-05-08 7:44 ` Gustavo Padovan
2012-05-08 7:57 ` Andrei Emeltchenko
2012-05-16 14:50 ` Andrei Emeltchenko [this message]
2012-05-16 15:56 ` Gustavo 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=20120516145037.GC10880@aemeltch-MOBL1 \
--to=andrei.emeltchenko.news@gmail.com \
--cc=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mathewm@codeaurora.org \
--cc=pkrystad@codeaurora.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).