[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131118145400.GE16735@n2100.arm.linux.org.uk>
Date: Mon, 18 Nov 2013 14:54:00 +0000
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Florian Meier <florian.meier@...lo.de>,
Stephen Warren <swarren@...dotorg.org>,
"Koul, Vinod" <vinod.koul@...el.com>,
"Williams, Dan J" <dan.j.williams@...el.com>,
devicetree <devicetree@...r.kernel.org>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
Liam Girdwood <lgirdwood@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Mark Brown <broonie@...nel.org>,
linux-rpi-kernel <linux-rpi-kernel@...ts.infradead.org>,
dmaengine <dmaengine@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCHv7] dmaengine: Add support for BCM2835
On Mon, Nov 18, 2013 at 04:30:17PM +0200, Andy Shevchenko wrote:
> On Mon, 2013-11-18 at 13:16 +0100, Florian Meier wrote:
> > >> + uint32_t chans_available;
> > >
> > > Why uint32_t?
> >
> > Because it is a bit mask of fixed length that directly comes from the
> > firmware.
>
> Like one already told you in your i2s patch, please, change that to
> corresponding u* value, namely u32.
There's no problem with uint32_t vs u32 - either will do. u32 is the
pre-stdint.h Linux definition of a 32-bit unsigned integer. There's
no reason why uint32_t isn't perfectly acceptable. It's a matter of
author taste which gets used. (Except where modifications are to an
existing chunk of code using one or the other - where consistency then
matters more.)
--
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