From: Johan Hedberg <johan.hedberg@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Fix error not being propagated properly
Date: Mon, 22 Mar 2010 13:11:20 +0200 [thread overview]
Message-ID: <20100322111120.GA5347@jh-x301> (raw)
In-Reply-To: <2d5a2c101003050536q61f16c12xb67a985234b3619@mail.gmail.com>
On Fri, Mar 05, 2010, Luiz Augusto von Dentz wrote:
> Now with the correct patch attached
>
> From 5dd57c233aa881faeaa6bfca147abcdb9e04dc93 Mon Sep 17 00:00:00 2001
> From: Luiz Augusto Von Dentz <luiz.dentz-von@nokia.com>
> Date: Fri, 5 Mar 2010 15:01:59 +0200
> Subject: [PATCH 11/11] Fix error not being propagated properly
>
> ---
> audio/headset.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
The first patch had some issues so I pushed my own fixed up version of
it. However, this second patch from you is now pushed (unchanged)
upstream.
Johan
prev parent reply other threads:[~2010-03-22 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 13:03 [PATCH] Fix error not being propagated properly Luiz Augusto von Dentz
2010-03-05 13:36 ` Luiz Augusto von Dentz
2010-03-22 11:11 ` 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=20100322111120.GA5347@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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;
as well as URLs for NNTP newsgroup(s).