From: David Miller <davem@davemloft.net>
To: hidave.darkstar@gmail.com
Cc: davej@codemonkey.org.uk, netdev@vger.kernel.org
Subject: Re: bluetooth lockdep trace. (.25rc5-git4)
Date: Mon, 31 Mar 2008 19:28:05 -0700 (PDT) [thread overview]
Message-ID: <20080331.192805.184855338.davem@davemloft.net> (raw)
In-Reply-To: <a8e1da0803290545r1a1652d6i506b146ccfe1dc65@mail.gmail.com>
From: "Dave Young" <hidave.darkstar@gmail.com>
Date: Sat, 29 Mar 2008 20:45:56 +0800
> Hi, I known this problem and did some work on this, but not finished
> due to lacking time.
>
> I will continue working on it when I'm free.
Thank you.
next prev parent reply other threads:[~2008-04-01 2:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 16:21 bluetooth lockdep trace. (.25rc5-git4) Dave Jones
2008-03-29 1:20 ` David Miller
2008-03-29 12:45 ` Dave Young
2008-04-01 2:28 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-01 8:58 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=20080331.192805.184855338.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=davej@codemonkey.org.uk \
--cc=hidave.darkstar@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).