[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM5PR0502MB299613C7F53BA5E02F46A47DAA840@AM5PR0502MB2996.eurprd05.prod.outlook.com>
Date: Tue, 22 Aug 2017 06:16:08 +0000
From: Noam Camus <noamca@...lanox.com>
To: Vineet Gupta <Vineet.Gupta1@...opsys.com>,
"linux-snps-arc@...ts.infradead.org"
<linux-snps-arc@...ts.infradead.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v3 07/11] ARC: [plat-eznps] new command line argument for
HW scheduler at MTM
>From: Vineet Gupta [mailto:Vineet.Gupta1@...opsys.com]
>Sent: Monday, August 21, 2017 20:04 PM
....
>> +
>> +/* Handle an out of bounds mtm hs counter value */ static void __init
>> +handle_mtm_hs_ctr_out_of_bounds_error(uint8_t val) {
>> + pr_err("** The value must be in range [%d,%d] (inclusive)\n",
>> + MT_HS_CNT_MIN, MT_HS_CNT_MAX);
>> +
>> + mtm_hs_ctr = val;
>This error handling doesn't make sense to me - if the value is not in range, why bother setting it at all. I'll fix it up locally.
Just look what we provide handle_mtm_hs_ctr_out_of_bounds_error() as parameter and it will be sensible to you :)
Noam
Powered by blists - more mailing lists