[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3F1D9DCAAB49B94D88DBE05911FA4E6E511095@039-SN1MPN1-006.039d.mgd.msft.net>
Date: Mon, 30 Jul 2012 09:29:15 +0000
From: Singh Sandeep-B37400 <B37400@...escale.com>
To: John Stoffel <john@...ffel.org>
CC: "linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"galak@...nel.crashing.org" <galak@...nel.crashing.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>
Subject: RE: [2/3][PATCH][v2] TDM Framework
-----Original Message-----
From: John Stoffel [mailto:john@...ffel.org]
Sent: 27 July 2012 19:42
To: Singh Sandeep-B37400
Cc: linuxppc-dev@...ts.ozlabs.org; linux-arm-kernel@...ts.infradead.org; galak@...nel.crashing.org; linux-kernel@...r.kernel.org; devel@...verdev.osuosl.org
Subject: Re: [2/3][PATCH][v2] TDM Framework
> From: Sandeep Singh <Sandeep@...escale.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.
[Sandeep] Patch for documentation for TDM is present in this patch set, which explains TDM in detail. Should we do this in commit message too??
Link too documentation patch: http://patchwork.ozlabs.org/patch/173680/
John
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists