From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752020AbdHXKow (ORCPT ); Thu, 24 Aug 2017 06:44:52 -0400 Received: from regular1.263xmail.com ([211.150.99.133]:48008 "EHLO regular1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751191AbdHXKov (ORCPT ); Thu, 24 Aug 2017 06:44:51 -0400 X-263anti-spam: KSV:0;BIG:0; X-MAIL-GRAY: 0 X-MAIL-DELIVERY: 1 X-KSVirus-check: 0 X-ADDR-CHECKED4: 1 X-ABS-CHECKED: 1 X-SKE-CHECKED: 1 X-ANTISPAM-LEVEL: 2 X-RL-SENDER: jeffy.chen@rock-chips.com X-FST-TO: broonie@kernel.org X-SENDER-IP: 103.29.142.67 X-LOGIN-NAME: jeffy.chen@rock-chips.com X-UNIQUE-TAG: <90aa193a48f89f9bad993c3c05901c58> X-ATTACHMENT-NUM: 0 X-DNS-TYPE: 0 Message-ID: <599EAE18.2030401@rock-chips.com> Date: Thu, 24 Aug 2017 18:44:40 +0800 From: jeffy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20130126 Thunderbird/19.0 MIME-Version: 1.0 To: Mark Brown CC: linux-kernel@vger.kernel.org, tiwai@suse.de, dolinux.peng@gmail.com, Jaroslav Kysela , alsa-devel@alsa-project.org, Takashi Iwai , Liam Girdwood Subject: Re: [PATCH] ASoC: Add a sanity check before using dai driver name References: <20170822144512.12976-1-jeffy.chen@rock-chips.com> <20170822161756.5h6smkjz6kkvl5i7@sirena.org.uk> <599CC17F.90806@rock-chips.com> <20170823110628.xergjdexrmxyqrza@sirena.org.uk> <599E4826.1060607@rock-chips.com> <20170824101826.htrevrhhgez2pgoe@sirena.org.uk> In-Reply-To: <20170824101826.htrevrhhgez2pgoe@sirena.org.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org hi Mark, On 08/24/2017 06:18 PM, Mark Brown wrote: > On Thu, Aug 24, 2017 at 11:29:42AM +0800, jeffy wrote: > >> and i was trying to do something like: >> if (dlc->dai_name && strcmp(dai->name, dlc->dai_name) >> && (!dai->driver->name || strcmp(dai->driver->name, dlc->dai_name))) >> continue; > >> which is add an accept case for: dai driver name is valid and matches the >> dai name we are looking for... > > Writing it as one if statement would at least be clearer. I can't > remember the patch you proposed at this point but the above looks > plausible. right, i've already post a v3 for that ;) >