On Mon, Apr 08, 2013 at 01:25:14PM +0100, Serban Constantinescu wrote:
> On 06/04/13 07:00, Greg KH wrote:
> >On Fri, Apr 05, 2013 at 04:17:47PM -0700, Arve Hjønnevåg wrote:
> >>On Thu, Apr 4, 2013 at 5:32 AM, Serban Constantinescu
> >> wrote:
> >>>
> >>>Since the binder driver uses both uint32_t
On 06/04/13 07:00, Greg KH wrote:
On Fri, Apr 05, 2013 at 04:17:47PM -0700, Arve Hjønnevåg wrote:
On Thu, Apr 4, 2013 at 5:32 AM, Serban Constantinescu
wrote:
Since the binder driver uses both uint32_t and unsigned int any further
kernel changes will be difficult to read. This patch fixes
On 06/04/13 07:00, Greg KH wrote:
On Fri, Apr 05, 2013 at 04:17:47PM -0700, Arve Hjønnevåg wrote:
On Thu, Apr 4, 2013 at 5:32 AM, Serban Constantinescu
serban.constantine...@arm.com wrote:
Since the binder driver uses both uint32_t and unsigned int any further
kernel changes will be difficult
On Mon, Apr 08, 2013 at 01:25:14PM +0100, Serban Constantinescu wrote:
On 06/04/13 07:00, Greg KH wrote:
On Fri, Apr 05, 2013 at 04:17:47PM -0700, Arve Hjønnevåg wrote:
On Thu, Apr 4, 2013 at 5:32 AM, Serban Constantinescu
serban.constantine...@arm.com wrote:
Since the binder driver uses
On Fri, Apr 05, 2013 at 04:17:47PM -0700, Arve Hjønnevåg wrote:
> On Thu, Apr 4, 2013 at 5:32 AM, Serban Constantinescu
> wrote:
> >
> > Since the binder driver uses both uint32_t and unsigned int any further
> > kernel changes will be difficult to read. This patch fixes the inconsistent
> >
On Fri, Apr 05, 2013 at 04:17:47PM -0700, Arve Hjønnevåg wrote:
On Thu, Apr 4, 2013 at 5:32 AM, Serban Constantinescu
serban.constantine...@arm.com wrote:
Since the binder driver uses both uint32_t and unsigned int any further
kernel changes will be difficult to read. This patch fixes the
On Thu, Apr 4, 2013 at 5:32 AM, Serban Constantinescu
wrote:
>
> Since the binder driver uses both uint32_t and unsigned int any further
> kernel changes will be difficult to read. This patch fixes the inconsistent
> types usage.
>
Would it make more sense to only change the types that need to
On Thu, Apr 4, 2013 at 5:32 AM, Serban Constantinescu
serban.constantine...@arm.com wrote:
Since the binder driver uses both uint32_t and unsigned int any further
kernel changes will be difficult to read. This patch fixes the inconsistent
types usage.
Would it make more sense to only change
Since the binder driver uses both uint32_t and unsigned int any further
kernel changes will be difficult to read. This patch fixes the inconsistent
types usage.
The patch does not change in any way the functionality of the binder driver.
Signed-off-by: Serban Constantinescu
---
Since the binder driver uses both uint32_t and unsigned int any further
kernel changes will be difficult to read. This patch fixes the inconsistent
types usage.
The patch does not change in any way the functionality of the binder driver.
Signed-off-by: Serban Constantinescu
10 matches
Mail list logo