From: "John Stoffel" <john@stoffel.org>
To: <sandeep@freescale.com>
Cc: <linuxppc-dev@lists.ozlabs.org>,
<linux-arm-kernel@lists.infradead.org>,
<galak@kernel.crashing.org>, <linux-kernel@vger.kernel.org>,
<devel@driverdev.osuosl.org>
Subject: Re: [2/3][PATCH][v2] TDM Framework
Date: Fri, 27 Jul 2012 10:11:33 -0400 [thread overview]
Message-ID: <20498.41365.853741.261834@quad.stoffel.home> (raw)
In-Reply-To: <1343397940-12975-1-git-send-email-sandeep@freescale.com>
> 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.
Please don't use TLAs (Three Letter Acronyms) like TDM without
explaining the clearly and up front. It makes it hard for anyone else
who doens't know your code to look it over without having to spend
lots of time poking around to figure it out from either context or
somewhere else.
John
next prev parent reply other threads:[~2012-07-27 14:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 14:05 sandeep
2012-07-27 14:05 ` [1/3][PATCH][v2] Adding documentation for TDM sandeep
2012-07-27 14:05 ` [3/3][PATCH][v2] Added TDM device support and Freescale Starlite driver sandeep
2012-07-27 14:11 ` John Stoffel [this message]
2012-07-30 9:29 ` [2/3][PATCH][v2] TDM Framework Singh Sandeep-B37400
2012-07-30 14:10 ` John Stoffel
2012-07-31 6:40 ` Singh Sandeep-B37400
2012-07-27 14:51 ` Russell King - ARM Linux
2012-07-30 13:00 ` Singh Sandeep-B37400
2012-07-27 15:25 ` Francois Romieu
2012-07-30 9:50 ` Singh Sandeep-B37400
2012-07-30 16:01 ` Greg KH
2012-08-01 12:13 ` Singh Sandeep-B37400
2012-08-01 12:37 ` Greg KH
2012-08-21 14:13 ` Mark Brown
2012-07-30 15:45 ` Mark Brown
2012-07-31 6:41 ` Singh Sandeep-B37400
2012-07-27 17:59 ` Greg KH
2012-07-30 9:10 ` Aggrwal Poonam-B10812
2012-07-30 16:04 ` Greg KH
2012-07-27 18:12 ` Greg KH
2012-07-30 9:13 ` 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=20498.41365.853741.261834@quad.stoffel.home \
--to=john@stoffel.org \
--cc=devel@driverdev.osuosl.org \
--cc=galak@kernel.crashing.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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
all inboxes | Powered by JetHome®