From: David Miller <davem@davemloft.net>
To: hidave.darkstar@gmail.com
Cc: marcel@holtmann.org, linux-kernel@vger.kernel.org,
bluez-devel@lists.sf.net, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] bluetooth : put hci dev after del conn
Date: Mon, 18 Feb 2008 20:44:57 -0800 (PST) [thread overview]
Message-ID: <20080218.204457.167455192.davem@davemloft.net> (raw)
In-Reply-To: <20080218075555.GA5940@darkstar.te-china.tietoenator.com>
From: Dave Young <hidave.darkstar@gmail.com>
Date: Mon, 18 Feb 2008 15:55:55 +0800
> Move hci_dev_put to del_conn to avoid hci dev going away before hci conn.
This looks correct so I have applied it.
> Signed-off-by: Dave Young <hidave.darkstar@gmail.com>
Please remove the extraneous space at the end of your
signoff line next time :-)
Also, I reworked the loop in del_conn() so that it no longer
generates a compile warning, so I had to apply your patch
by hand.
next prev parent reply other threads:[~2008-02-19 4:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 7:55 [PATCH 1/2] bluetooth : put hci dev after del conn Dave Young
2008-02-19 4:44 ` David Miller [this message]
2008-02-20 0:17 ` Dave Young
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=20080218.204457.167455192.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bluez-devel@lists.sf.net \
--cc=hidave.darkstar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.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