On Fri, 2012-11-30 at 14:38 +0800, Shan Wei wrote:
> Shan Wei said, at 2012/11/16 16:34:
> > Shan Wei said, at 2012/11/13 9:53:
> >> From: Shan Wei
> >>
> >> typeof(&buffer) is a pointer to array of 1024 char, or char (*)[1024].
> >> But, typeof(&buffer[0]) is a pointer to char which match the ret
Shan Wei said, at 2012/11/16 16:34:
> Shan Wei said, at 2012/11/13 9:53:
>> From: Shan Wei
>>
>> typeof(&buffer) is a pointer to array of 1024 char, or char (*)[1024].
>> But, typeof(&buffer[0]) is a pointer to char which match the return type of
>> get_trace_buf().
>> As well-known, the value of
Shan Wei said, at 2012/11/13 9:53:
> From: Shan Wei
>
> typeof(&buffer) is a pointer to array of 1024 char, or char (*)[1024].
> But, typeof(&buffer[0]) is a pointer to char which match the return type of
> get_trace_buf().
> As well-known, the value of &buffer is equal to &buffer[0].
> so retur
From: Shan Wei
typeof(&buffer) is a pointer to array of 1024 char, or char (*)[1024].
But, typeof(&buffer[0]) is a pointer to char which match the return type of
get_trace_buf().
As well-known, the value of &buffer is equal to &buffer[0].
so return this_cpu_ptr(&percpu_buffer->buffer[0]) can avo
4 matches
Mail list logo
