From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.2 required=3.0 tests=DATE_IN_PAST_03_06, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9EBA2C10F25 for ; Mon, 9 Mar 2020 22:07:09 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 2E91924654 for ; Mon, 9 Mar 2020 22:07:09 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="fKRsyM6S" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2E91924654 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 733DF1607; Mon, 9 Mar 2020 23:06:17 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 733DF1607 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1583791627; bh=1xQu1uFYnA5P7YZ7rWcLoLBBSvO7bdraHEbRcRh9Dws=; h=Subject:To:References:From:Date:In-Reply-To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=fKRsyM6SblgGdbTeJVct416zrTmPvtbv7T+HmbVU5lrlXLGsxO5mEj3Wa+4rt0TzB zLMHc9+gVlYg/7gE3yB92yXDKVzDaegipVImTpa5NeFpi5O34MbHVbXPruje3FQAH4 M9dGdpp7cZZEHl80h+KyM7Bz6fHT3nJH7BpWR3WA= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id A8444F801F8; Mon, 9 Mar 2020 23:06:16 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 41245F801F7; Mon, 9 Mar 2020 23:06:12 +0100 (CET) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id E51F0F800DA for ; Mon, 9 Mar 2020 23:06:07 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz E51F0F800DA X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Mar 2020 15:06:04 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.70,534,1574150400"; d="scan'208";a="388711021" Received: from bnkannan-mobl.amr.corp.intel.com (HELO [10.254.6.234]) ([10.254.6.234]) by orsmga004.jf.intel.com with ESMTP; 09 Mar 2020 15:06:03 -0700 Subject: Re: [PATCH 4/7] ASoC: Intel: Skylake: Shield against no-NHLT configurations To: Cezary Rojewski , alsa-devel@alsa-project.org References: <20200305145314.32579-1-cezary.rojewski@intel.com> <20200305145314.32579-5-cezary.rojewski@intel.com> <7f74b049-4659-9656-4396-3c1b42d2e32c@linux.intel.com> <2a380994-a723-ea25-7feb-6a650a3889e3@intel.com> <740bc65e-afe9-cefe-4a31-d19cc9d83c56@intel.com> From: Pierre-Louis Bossart Message-ID: <7fe9e0d3-92b7-4464-b490-a5e69a5815b4@linux.intel.com> Date: Mon, 9 Mar 2020 13:40:24 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <740bc65e-afe9-cefe-4a31-d19cc9d83c56@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Cc: vkoul@kernel.org, broonie@kernel.org, tiwai@suse.com, lgirdwood@gmail.com X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On 3/9/20 12:38 PM, Cezary Rojewski wrote: > On 2020-03-09 18:01, Pierre-Louis Bossart wrote: >> On 3/9/20 8:03 AM, Cezary Rojewski wrote: >>> On 2020-03-06 22:03, Pierre-Louis Bossart wrote: >>>> >>>> >>>>> -    intel_nhlt_free(skl->nhlt); >>>>> +    if (skl->nhlt) >>>>> +        intel_nhlt_free(skl->nhlt); >>>> >>>> we could alternatively move the test in intel_nhlt_free, which seems >>>> like a more robust thing to do? >>> >>> Depends. In general kernel-internal API trusts its caller and >>> appending 'ifs' everywhere would unnecessarily slow entire kernel >>> down. While intel_nhlt_free is called rarely, I'd still argue caller >>> should be sane about its invocation. >>> >>> 'if' in skl_probe could be avoided had the function's structure been >>> better. 'if' in skl_remove is just fine, though. >>> >>> Let's leave it as is. >> >> it's also used in SOF: >> >> sound/soc/sof/intel/hda.c:              intel_nhlt_free(nhlt); >> >> that's why I suggested to factor the test so that both users don't >> need to add the if. > > I understand, and my explanation still applies. > > SOF's intel_nhlt_free usage is great example actually. Caller is sane > about its doings as it should be. Internal API needs not to suffer from > callers irresponsibility. ok, indeed looking at the code there's no need for the test.