Hi,
On 12 January 2015 at 21:58, Jaehoon Chung wrote:
> Hi.
>
> On 01/13/2015 02:40 PM, Akshay Saraswat wrote:
>> Hi,
>>
>>> Hi,
>>>
>>>
>>> On 01/13/2015 11:56 AM, Simon Glass wrote:
Hi,
On 12 January 2015 at 18:51, Joonyoung Shim
wrote:
> Hi,
>
> On 01/13/2015
Hi.
On 01/13/2015 02:40 PM, Akshay Saraswat wrote:
> Hi,
>
>> Hi,
>>
>>
>> On 01/13/2015 11:56 AM, Simon Glass wrote:
>>> Hi,
>>>
>>> On 12 January 2015 at 18:51, Joonyoung Shim wrote:
Hi,
On 01/13/2015 11:47 AM, Simon Glass wrote:
> Hi,
>
> On 12 January 2015 at 18:36
Hi Akshay,
On 01/13/2015 02:40 PM, Akshay Saraswat wrote:
> Hi,
>
>> Hi,
>>
>>
>> On 01/13/2015 11:56 AM, Simon Glass wrote:
>>> Hi,
>>>
>>> On 12 January 2015 at 18:51, Joonyoung Shim wrote:
Hi,
On 01/13/2015 11:47 AM, Simon Glass wrote:
> Hi,
>
> On 12 January 2015 a
Hi,
>Hi,
>
>
>On 01/13/2015 11:56 AM, Simon Glass wrote:
>> Hi,
>>
>> On 12 January 2015 at 18:51, Joonyoung Shim wrote:
>>> Hi,
>>>
>>> On 01/13/2015 11:47 AM, Simon Glass wrote:
Hi,
On 12 January 2015 at 18:36, Joonyoung Shim
wrote:
> Hi,
>
> On 01/13/2015 11:
Hi,
On 01/13/2015 11:56 AM, Simon Glass wrote:
> Hi,
>
> On 12 January 2015 at 18:51, Joonyoung Shim wrote:
>> Hi,
>>
>> On 01/13/2015 11:47 AM, Simon Glass wrote:
>>> Hi,
>>>
>>> On 12 January 2015 at 18:36, Joonyoung Shim wrote:
Hi,
On 01/13/2015 11:27 AM, Simon Glass wrote:
>
Hi,
On 12 January 2015 at 18:51, Joonyoung Shim wrote:
> Hi,
>
> On 01/13/2015 11:47 AM, Simon Glass wrote:
>> Hi,
>>
>> On 12 January 2015 at 18:36, Joonyoung Shim wrote:
>>> Hi,
>>>
>>> On 01/13/2015 11:27 AM, Simon Glass wrote:
Hi,
On 12 January 2015 at 18:24, Joonyoung Shim
Hi,
On 01/13/2015 11:47 AM, Simon Glass wrote:
> Hi,
>
> On 12 January 2015 at 18:36, Joonyoung Shim wrote:
>> Hi,
>>
>> On 01/13/2015 11:27 AM, Simon Glass wrote:
>>> Hi,
>>>
>>> On 12 January 2015 at 18:24, Joonyoung Shim wrote:
Hi,
I found below compile warnings,
C
Hi,
On 12 January 2015 at 18:36, Joonyoung Shim wrote:
> Hi,
>
> On 01/13/2015 11:27 AM, Simon Glass wrote:
>> Hi,
>>
>> On 12 January 2015 at 18:24, Joonyoung Shim wrote:
>>> Hi,
>>>
>>> I found below compile warnings,
>>>
>>> CC arch/arm/cpu/armv7/exynos/clock.o
>>> arch/arm/cpu/armv7/e
Hi,
On 01/13/2015 11:27 AM, Simon Glass wrote:
> Hi,
>
> On 12 January 2015 at 18:24, Joonyoung Shim wrote:
>> Hi,
>>
>> I found below compile warnings,
>>
>> CC arch/arm/cpu/armv7/exynos/clock.o
>> arch/arm/cpu/armv7/exynos/clock.c: In function ‘clock_get_periph_rate’:
>> arch/arm/cpu/ar
Hi,
On 12 January 2015 at 18:24, Joonyoung Shim wrote:
> Hi,
>
> I found below compile warnings,
>
> CC arch/arm/cpu/armv7/exynos/clock.o
> arch/arm/cpu/armv7/exynos/clock.c: In function ‘clock_get_periph_rate’:
> arch/arm/cpu/armv7/exynos/clock.c:265:47: warning: array subscript is above
Hi,
I found below compile warnings,
CC arch/arm/cpu/armv7/exynos/clock.o
arch/arm/cpu/armv7/exynos/clock.c: In function ‘clock_get_periph_rate’:
arch/arm/cpu/armv7/exynos/clock.c:265:47: warning: array subscript is above
array bounds [-Warray-bounds]
struct clk_bit_info *bit_info = &clk
11 matches
Mail list logo