-----Original Message-----
From: John Stoffel [mailto:<redacted>]=20
Sent: Monday, July 30, 2012 7:40 PM
To: Singh Sandeep-B37400
Cc: John Stoffel; <redacted>; <redacted>
radead.org; galak@kernel.crashing.org; linux-kernel@vger.kernel.org; devel@=
driverdev.osuosl.org
Subject: RE: [2/3][PATCH][v2] TDM Framework
quoted
quoted
quoted
quoted
"Singh" =3D=3D Singh Sandeep-B37400 [off-list ref] writes:
Singh> -----Original Message-----
Singh> From: John Stoffel [mailto:john@stoffel.org]
Singh> Sent: 27 July 2012 19:42
Singh> To: Singh Sandeep-B37400
Singh> Cc: linuxppc-dev@lists.ozlabs.org;=20
Singh> linux-arm-kernel@lists.infradead.org; galak@kernel.crashing.org;=20
Singh> linux-kernel@vger.kernel.org; devel@driverdev.osuosl.org
Singh> Subject: Re: [2/3][PATCH][v2] TDM Framework
quoted
From: Sandeep Singh <redacted> TDM Framework is an=20
attempt to provide a platform independent layer which can offer a=20
standard interface for TDM access to different client modules.
Singh> Please don't use TLAs (Three Letter Acronyms) like TDM without expla=
ining 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 poki=
ng around to figure it out from either context or somewhere else.
Singh> [Sandeep] Patch for documentation for TDM is present in this=20
Singh> patch set, which explains TDM in detail. Should we do this in=20
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 al=
so into the Kconfig text, so that someone configuring the kernel has a clue=
what you're talking about. =20
[Sandeep] Thanks for suggestion. Will take care.
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