From: Josh Boyer <jwboyer@gmail.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: sandeep@freescale.com, linuxppc-dev@lists.ozlabs.org,
Poonam Aggrwal <poonam.aggrwal@freescale.com>
Subject: Re: [PATCH][upstream] TDM Framework
Date: Fri, 20 Jul 2012 09:27:03 -0400 [thread overview]
Message-ID: <CA+5PVA7XSv7Fbg8DLCZMPmOzMX6uDnxzsAna2gW4RCfH7=eCUg@mail.gmail.com> (raw)
In-Reply-To: <1342788865.28608.0.camel@concordia>
On Fri, Jul 20, 2012 at 8:54 AM, Michael Ellerman
<michael@ellerman.id.au> wrote:
> On Fri, 2012-07-20 at 18:05 +0530, sandeep@freescale.com wrote:
>> From: Sandeep Singh <Sandeep@freescale.com>
>>
>> TDM Framework is an attempt to provide a platform independent layer which can
>> offer a standard interface for TDM access to different client modules.
>> Beneath, the framework layer can house different types of TDM drivers to handle
>> various TDM devices, the hardware intricacies of the devices being completely
>> taken care by TDM drivers.
>
> TDM ?
And here I was thinking I was the only one scratching his head. All I
could come up with was Time Division Multiplexing.
Protip: If you use an acronym a billion times in a patch, expand it at
least in one place.
josh
next prev parent reply other threads:[~2012-07-20 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 12:35 [PATCH][upstream] TDM Framework sandeep
2012-07-20 12:35 ` [PATCH][upstream]Added TDM device support and Freescale Starlite driver sandeep
2012-07-20 12:54 ` [PATCH][upstream] TDM Framework Michael Ellerman
2012-07-20 13:27 ` Josh Boyer [this message]
2012-07-21 7:36 ` Aggrwal Poonam-B10812
2012-07-21 9:20 ` Aggrwal Poonam-B10812
2012-07-20 14:50 ` Stephen Rothwell
2012-07-21 7:36 ` Aggrwal Poonam-B10812
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='CA+5PVA7XSv7Fbg8DLCZMPmOzMX6uDnxzsAna2gW4RCfH7=eCUg@mail.gmail.com' \
--to=jwboyer@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=poonam.aggrwal@freescale.com \
--cc=sandeep@freescale.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).