From: Johan Hedberg <johan.hedberg@gmail.com>
To: Szymon Janc <szymon.janc@tieto.com>
Cc: linux-bluetooth@vger.kernel.org, kanak.gupta@stericsson.com
Subject: Re: [PATCH 1/2] Remove dead code from bonding_request_new
Date: Mon, 23 Jan 2012 12:56:17 +0200 [thread overview]
Message-ID: <20120123105617.GC13100@x220> (raw)
In-Reply-To: <1327073187-1009-1-git-send-email-szymon.janc@tieto.com>
Hi Szymon,
On Fri, Jan 20, 2012, Szymon Janc wrote:
> agent_create always return valid pointer so there is not need to check
> for NULL as this will never happen.
> ---
> src/device.c | 9 +--------
> 1 files changed, 1 insertions(+), 8 deletions(-)
Both patches have been applied. Thanks.
Johan
prev parent reply other threads:[~2012-01-23 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 15:26 [PATCH 1/2] Remove dead code from bonding_request_new Szymon Janc
2012-01-20 15:26 ` [PATCH 2/2] Remove dead code from device_create_bonding Szymon Janc
2012-01-23 10: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=20120123105617.GC13100@x220 \
--to=johan.hedberg@gmail.com \
--cc=kanak.gupta@stericsson.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=szymon.janc@tieto.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).