[2/3][PATCH][v2] TDM Framework

From
John Stoffel <hidden>
Date
2012-07-30 14:11:32
Also in
linuxppc-dev, lkml
Reply to
Singh Sandeep-B37400, 2012-07-30
quoted
quoted
quoted
quoted
"Singh" == Singh Sandeep-B37400 [off-list ref] writes:
Singh> -----Original Message-----
Singh> From: John Stoffel [mailto:john at stoffel.org] 
Singh> Sent: 27 July 2012 19:42
Singh> To: Singh Sandeep-B37400
Singh> Cc: linuxppc-dev at lists.ozlabs.org; linux-arm-kernel at lists.infradead.org; galak at kernel.crashing.org; linux-kernel at vger.kernel.org; devel at driverdev.osuosl.org
Singh> Subject: Re: [2/3][PATCH][v2] TDM Framework

quoted
From: Sandeep Singh <redacted> TDM Framework is an 
attempt to provide a platform independent layer which can offer a 
standard interface  for TDM access to different client modules.
Singh> 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.

Singh> [Sandeep] Patch for documentation for TDM is present in this
Singh> patch set, which explains TDM in detail. Should we do this in
Singh> commit message too??  Link too documentation patch:
Singh> http://patchwork.ozlabs.org/patch/173680/

You should put the expansion of TDM into the initial commit message,
and also into the Kconfig text, so that someone configuring the kernel
has a clue what you're talking about.  

Try to approach this as a brandnew user who doesn't have your
knowledge of the software.  Write for the un-initiated if at all
possible.

John
Thread (22 messages) 22 messages, 9 authors, last reply 2012-08-21
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help