Subject: [PATCH v2] ARM: OMAP2: use 'int' instead of 'unsigned' for variable 'gpmc_irq_start'

From: [email-masked] (Tony Lindgren)
Date: Thu, 22 Aug 2013 01:32:06 -0700

* Chen Gang <[email-masked]> [130822 01:10]:
> On 08/22/2013 03:57 PM, Tony Lindgren wrote:
> > * Chen Gang <[email-masked]> [130822 00:55]:
> >> 'gpmc_irq_start' is mostly used as 'int', and for a variable, do not
> >> suggest to only use 'unsigned' as its type, so use 'int' instead of
> >> 'unsigned' for variable 'gpmc_irq_start'.
> >>
> >> Also it will fix the related issue (dummy the real world failure):
> >>
> >>   arch/arm/mach-omap2/gpmc.c:728:2: warning: comparison of unsigned expression < 0 is always false [-Wtype-limits]
> >>
> > 
> > Thanks applying into omap-for-v3.12/fixes-non-critical.
> > 
> 
> Thank you too.
> 
> Hmm... excuse me, I am not quite familiar with the omap version trees,
> so may have a doubt: "it seems this is a real bug, is it suitable to
> belong to fixes-none-critical tree ?"

For the -rc cycle we try to limit the patches to oopses and regressions,
especially this close to v3.11 being tagged.

It seems the bug has been there for quite some time, and that we don't
seem to have oopses or other failures reporting this. So it seems there's
no reason for urgency to have it merged into the current -rc series.

If you (or somebody else) strongly feels that it should be in applied
to the current -rc series as a fix instead of during the merge window,
then please let me know the failing cases with logs showing what
happens.

Regards,

Tony