From: Marcel Holtmann <marcel@holtmann.org>
To: "Gustavo F. Padovan" <padovan@profusion.mobi>
Cc: Haijun Liu <Haijun.Liu@Atheros.com>,
"(linux-bluetooth@vger.kernel.org)"
<linux-bluetooth@vger.kernel.org>,
Dan Tian <Dan.Tian@Atheros.com>
Subject: Re: Do you have a plan to split ERTM into a separate file?
Date: Tue, 01 Mar 2011 23:26:25 -0800 [thread overview]
Message-ID: <1299050785.2519.63.camel@aeonflux> (raw)
In-Reply-To: <20110228171941.GA2165@joana>
Hi Gustavo,
> > Do you have a plan to split ERTM code into a separate file?
> > It may be easier to read/learn ERTM mechanism with loosely coupled code for people.
> > Thank you! :)
>
> I don't. But I'll be happy if you send me patches for that. ;)
this is actually a bad idea. So lets not even go there.
Regards
Marcel
next prev parent reply other threads:[~2011-03-02 7:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6AAC4214B9104E409FF4885ACB62A96101A6A6762B@SHEXMB-01.global.atheros.com>
2011-02-28 17:19 ` Do you have a plan to split ERTM into a separate file? Gustavo F. Padovan
2011-03-02 7:26 ` Marcel Holtmann [this message]
2011-02-24 13:23 Haijun Liu
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=1299050785.2519.63.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=Dan.Tian@Atheros.com \
--cc=Haijun.Liu@Atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=padovan@profusion.mobi \
/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).