On Fri, 24 Oct 2014 18:31:21 +0200 Michal Nazarewicz <min...@mina86.com> wrote:
> On Wed, Oct 22 2014, Pintu Kumar <pint...@samsung.com> wrote: > > This patch include CMA info (CMATotal, CMAFree) in /proc/meminfo. > > Currently, in a CMA enabled system, if somebody wants to know the > > total CMA size declared, there is no way to tell, other than the dmesg > > or /var/log/messages logs. > > With this patch we are showing the CMA info as part of meminfo, so that > > it can be determined at any point of time. > > This will be populated only when CMA is enabled. > > > > Below is the sample output from a ARM based device with RAM:512MB and > > CMA:16MB. > > > > MemTotal: 471172 kB > > MemFree: 111712 kB > > MemAvailable: 271172 kB > > . > > . > > . > > CmaTotal: 16384 kB > > CmaFree: 6144 kB > > > > This patch also fix below checkpatch errors that were found during these > > changes. > > As already mentioned, this should be in separate patch. Yes, in theory. But a couple of little whitespace fixes aren't really worth a resend. As long as they don't make the patch harder to read and to backport I usually just let them through. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
