[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d2a9f155-f309-0182-73c9-5c02d7014574@acm.org>
Date: Wed, 22 Apr 2020 18:21:13 -0700
From: Bart Van Assche <bvanassche@....org>
To: Walter Wu <walter-zh.wu@...iatek.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
wsd_upstream <wsd_upstream@...iatek.com>
Subject: Re: [PATCH v2] stacktrace: cleanup inconsistent variable type
On 4/20/20 6:35 PM, Walter Wu wrote:
> Modify the variable type of 'skip' member of struct stack_trace.
> In theory, the 'skip' variable type should be unsigned int.
> There are two reasons:
> - The 'skip' only has two situation, 1)Positive value, 2)Zero
> - The 'skip' of struct stack_trace has inconsistent type with struct
> stack_trace_data, it makes a bit confusion in the relationship between
> struct stack_trace and stack_trace_data.
Reviewed-by: Bart Van Assche <bvanassche@....org>
Powered by blists - more mailing lists