Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752529AbbGWJYa (ORCPT ); Thu, 23 Jul 2015 05:24:30 -0400 Received: from e28smtp07.in.ibm.com ([122.248.162.7]:41252 "EHLO e28smtp07.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751173AbbGWJYW (ORCPT ); Thu, 23 Jul 2015 05:24:22 -0400 X-Helo: d28dlp03.in.ibm.com X-MailFrom: maddy@linux.vnet.ibm.com X-RcptTo: linux-kernel@vger.kernel.org Message-ID: <55B0B2A0.30404@linux.vnet.ibm.com> Date: Thu, 23 Jul 2015 14:53:44 +0530 From: Madhavan Srinivasan User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Michael Ellerman CC: Anshuman Khandual , linux-kernel@vger.kernel.org, Stephane Eranian , Paul Mackerras , Anton Blanchard , Sukadev Bhattiprolu , linuxppc-dev@lists.ozlabs.org, Daniel Axtens Subject: Re: [PATCH v5 4/7] powerpc/powernv: detect supported nest pmus and its events References: <1437045206-7491-1-git-send-email-maddy@linux.vnet.ibm.com> <1437045206-7491-5-git-send-email-maddy@linux.vnet.ibm.com> <1437538064.30906.20.camel@axtens.net> <55B083A2.4030404@linux.vnet.ibm.com> <1437642672.29271.2.camel@ellerman.id.au> In-Reply-To: <1437642672.29271.2.camel@ellerman.id.au> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15072309-0025-0000-0000-000005FFE8D5 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1671 Lines: 44 On Thursday 23 July 2015 02:41 PM, Michael Ellerman wrote: > On Thu, 2015-07-23 at 11:33 +0530, Madhavan Srinivasan wrote: >> On Wednesday 22 July 2015 09:37 AM, Daniel Axtens wrote: >>> >>>> static struct perchip_nest_info p8_nest_perchip_info[P8_NEST_MAX_CHIPS]; >>>> +static struct nest_pmu *per_nest_pmu_arr[P8_NEST_MAX_PMUS]; >>>> + >>>> +static int nest_event_info(struct property *pp, char *name, >>>> + struct nest_ima_events *p8_events, int string, u32 val) >>> 'int string' is a bit confusing. 'bool is_string' might be clearer, but >>> I think it would be even better still to have different functions for >>> string and non-string cases, especially because you only need val in the >>> non-string case. >> I would perfer to be a single function, since most of the code is same >> just of the sting or val part. yes. We can make is as is_string and will >> add comment explaining what is done here? > I think Daniel's right, it would be better as two functions. > > The only part that is common after the if (string) check is the > p8_events->ev_value = buf assignment. > > So you should be able to keep all the code up to the if (string) check in a > shared function and just have two wrappers that use it. > > cheers Sure. Will do. Maddy > > > _______________________________________________ > Linuxppc-dev mailing list > Linuxppc-dev@lists.ozlabs.org > https://lists.ozlabs.org/listinfo/linuxppc-dev -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/