Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp862894pxf; Wed, 7 Apr 2021 13:34:33 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzKBqtjnKU5Ci5PY21s+bgSxgyk8/2phDoC+y7KW6e2zm6/1gZRcc2l8juM78Li5Oqh9rWs X-Received: by 2002:a17:906:7946:: with SMTP id l6mr5867295ejo.500.1617827673391; Wed, 07 Apr 2021 13:34:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617827673; cv=none; d=google.com; s=arc-20160816; b=QgsOqtc90UwMRTsONRmLpzLCl0/BAdUEmU1ZM1+1hWKymRXMDRoYKKSycpnzUbj6g0 oPahEeg6LPiKueti30nZoZs/n919XYDxZQOS/LrDZ5OjaYbXfi66b92QKwBoz6WBWCZg CL5wFmyv15Bz8BxtzGoyYZ2Vmnu2xXcU+8QurFXkOUyF9a/wjjJNBFPT0XwM9sDFTh41 dggKpyqGVCbWnt/qi9Dpi/QKW9LIGqMzybnFFnXUAPPmuN+n0clO1kOFYXytQuvcgRyd LRmuvfKoRHiTeyEzVi5s8hEv6/mf5oaGjSmfvE0ulpUB28O66CH++oqkqFDA2Omxv+F6 B1rw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:to:subject; bh=dO0Y5WPajZpaQOtUpGSC6SKrJjW1J7C7v4i2o7HD58A=; b=AiASo4qTu0XNBEOshYkxMR51NaFdvoXi8177tp/alU3gMawAz2jDqlXh3SQi+Sr+vv BKaWCtPiXtcB9gdIh0eYiXUxta44WF+vYL1j2URXJiD+yggNISeKLPfnHAXXMKKrqNRd e3BsquLKF1SFcIUddsUpodZ5mwXuBNR6hYnDclEDeuinxQW1V04xPgIVaH0Qe/WhYDrV vjBZM2QBBobP4CqjZ1MNACFQdS71d6mnUgv/VQX0jpq1ZlO9yh+foy4aegpYnIR2aOSl SHsmmnahkwvDsxXVctFwuiMPIhHyERODRf95riBlH7SrAGB7TJpRoVY8CyeLIJKKLT5i 7Ujw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=hisilicon.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m7si6356791edc.326.2021.04.07.13.34.09; Wed, 07 Apr 2021 13:34:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=hisilicon.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240282AbhDGIS4 (ORCPT + 99 others); Wed, 7 Apr 2021 04:18:56 -0400 Received: from szxga07-in.huawei.com ([45.249.212.35]:16808 "EHLO szxga07-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239849AbhDGISz (ORCPT ); Wed, 7 Apr 2021 04:18:55 -0400 Received: from DGGEMS410-HUB.china.huawei.com (unknown [172.30.72.58]) by szxga07-in.huawei.com (SkyGuard) with ESMTP id 4FFcg45l8gz7tPr; Wed, 7 Apr 2021 16:16:32 +0800 (CST) Received: from [127.0.0.1] (10.69.38.196) by DGGEMS410-HUB.china.huawei.com (10.3.19.210) with Microsoft SMTP Server id 14.3.498.0; Wed, 7 Apr 2021 16:18:37 +0800 Subject: Re: [PATCH v6 3/5] i2c: add support for HiSilicon I2C controller To: Wolfram Sang , , , , , , , , , , , , , References: <1617197790-30627-1-git-send-email-yangyicong@hisilicon.com> <1617197790-30627-4-git-send-email-yangyicong@hisilicon.com> <20210406200248.GH3122@kunai> From: Yicong Yang Message-ID: <5c64a396-05ca-d19f-04ca-a3770e82c009@hisilicon.com> Date: Wed, 7 Apr 2021 16:18:37 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1 MIME-Version: 1.0 In-Reply-To: <20210406200248.GH3122@kunai> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.69.38.196] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021/4/7 4:02, Wolfram Sang wrote: > > Only super minor stuff. Thanks to all the contributors and reviewers! > >> +#define HZ_PER_KHZ 1000 > > KHZ_PER_HZ? that doesn't match what we want. we want the count of HZs per one KHZ. > >> + ret = devm_i2c_add_adapter(dev, adapter); >> + if (ret) { >> + dev_err(dev, "failed to add i2c adapter, ret = %d\n", ret); > > No need to print that. The core prints messages on failures. > i check the code and find a little difference. the print in the core doesn't have the device prefix so it may not tell us which device's registeration fails. but considering we have device name embedded in the adapter name for this driver, it's ok to remove this message.