Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp120796ybl; Mon, 12 Aug 2019 12:53:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqwpUvjZVw1nzRJHShTFXmiWiN3G0l67IYhesteUv0PdnOM3uC+rLXMuiXWVl4NeUNx5FIy6 X-Received: by 2002:a17:902:e282:: with SMTP id cf2mr34783475plb.301.1565639587687; Mon, 12 Aug 2019 12:53:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565639587; cv=none; d=google.com; s=arc-20160816; b=mTc0w8UKxN9zmXrC8ntuMed6GMeIn/oPprDqxwPzG+M6AlKAnbjlggKiTRgaHgLH/8 9R0X5pSufnaPQmF2Am/WyPnxKDHSP0tQ4L89NlMKR+YkpjJ6n0YXEsNJ1KBTcDBWwxVt jSjYD/IaGszdCbqmNj0Lmjsh1sE6Ab1qcjuxkh8ZHGtcMhcKq86RjrRV/zsTnN2J+ALW kmp+3zWGVNfOkbPkd4FBxm2E4kG+UHYy1QhF7HsuDxSKakGpIhg9AVu73C7UTULrrFnL NuxmJeZqS215pITjrQuXxj3ucdISVkTVkEE8ypa06dXCXWkoiX3JWZAbxphhWaQege0v 91Qw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:dkim-signature; bh=kEkVLWwqovwyFjtoRAd3ZuRhWq4pA+S9mUWyYQC3ODQ=; b=mqAGwlOcHV86GNbi0m8fM/IyLiZePiUSLCvyD9sc5uBJw/pE2Uq3xOJxszPJ+Qf/PZ Nf06UDHC8xzS/f/jcXHLTxV82ogsOHL9qjKtsK2VSQF2akEOTc0Nn4ip3Gfs6iIMmi25 Mhp4ill4BQskWqOBH/F7ebWsZ+jXGgDbMK723gYUJ9iGLCRJ8GRe2+zblUyJ+2QSlZmM WKeg8UNfWqcoClSI7Td5jSj5aW8mnZPxfSZ2l4+PSo9ZjZxki3Oy9WK3ofE2+RjsMjpH 2/kwPhV1j/LqrE9IHVavHIDn2FXJaRgCeFf5RJztylCJd1RtEEAT3IMEQDaqMlmerwR2 E+yQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@netronome-com.20150623.gappssmtp.com header.s=20150623 header.b=Go1xYdCn; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w11si61928542pgr.321.2019.08.12.12.52.51; Mon, 12 Aug 2019 12:53:07 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@netronome-com.20150623.gappssmtp.com header.s=20150623 header.b=Go1xYdCn; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727017AbfHLTwN (ORCPT + 99 others); Mon, 12 Aug 2019 15:52:13 -0400 Received: from mail-qt1-f194.google.com ([209.85.160.194]:32772 "EHLO mail-qt1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726940AbfHLTwM (ORCPT ); Mon, 12 Aug 2019 15:52:12 -0400 Received: by mail-qt1-f194.google.com with SMTP id v38so11701697qtb.0 for ; Mon, 12 Aug 2019 12:52:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netronome-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :organization:mime-version:content-transfer-encoding; bh=kEkVLWwqovwyFjtoRAd3ZuRhWq4pA+S9mUWyYQC3ODQ=; b=Go1xYdCnowLCjBoQHanBZc7stvpdCA4G/sIQJnrvYOMObBB2RF6oSbhmlUQOeUImJi FjU3UE6ZPgHFVoFvHQajdt5DYsYDsfr3MtE4zVRqViB/uQewO2eXWYVzND9A6/k4syDI KiQJ6kbVnAeos66Zydq4l49v2EO55bXWiaIY8YW1yEmsocbSrMGpDqu+fWwU8vgoLsAL BjBZUWdKUw5Ietmf5bF6Q/S0JeYR6CXwsVmVc2s/Qsj4Yz5gyHXdmhwnwpT0kgnEBwjL P516qLnaRnN3sZ9sXUHu8h9MiftUXkp2Ylvq4VMfyG9py3890rhln94s9T5uukkQHTwY uSiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:organization:mime-version:content-transfer-encoding; bh=kEkVLWwqovwyFjtoRAd3ZuRhWq4pA+S9mUWyYQC3ODQ=; b=hU41BvkKk7IkhX7GvSjJLzSfIhux+vfEML+Re8cWCxr1tHaecFJVzaNOLRgUNkqAHp ggsuHR7hDlw5LFIXj6SB+m5xq5xDqOG5LJ0ihNPpigLit75njlISXqy2XcvrCy/F3xl8 hE2sGgTB7xjBuBiZz/aZHb4oIKq93EZOy+lFSbYuvHY7fT0eZyBl4kBhxtE+EKTKgkM6 tZTSmyPdpdMgK+16eJgMitlFhpyz8ET5HjAo/Jc0Xlap8yMiMqU15tZksVMRAdzCohER kMdTVtoPgmU4BasprI/JwkqeGV4vH0DMuPrY6Gt6n5jvgsG5FuiVKaOuDyR7hrWB05H5 beog== X-Gm-Message-State: APjAAAXNBuB4q9K9TGiBP7jffCKmgpT2+d4+MR8qnhBg8h+TF+63WF9x PeSp5GvZX1psIhYlm0UgzSiKZg== X-Received: by 2002:ac8:376c:: with SMTP id p41mr11767771qtb.306.1565639531882; Mon, 12 Aug 2019 12:52:11 -0700 (PDT) Received: from cakuba.netronome.com ([66.60.152.14]) by smtp.gmail.com with ESMTPSA id g24sm3920710qtc.38.2019.08.12.12.52.09 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Mon, 12 Aug 2019 12:52:11 -0700 (PDT) Date: Mon, 12 Aug 2019 12:52:02 -0700 From: Jakub Kicinski To: Thomas Bogendoerfer Cc: Ralf Baechle , Paul Burton , James Hogan , Dmitry Torokhov , Lee Jones , "David S. Miller" , Srinivas Kandagatla , Alessandro Zummo , Alexandre Belloni , Greg Kroah-Hartman , Jiri Slaby , Evgeniy Polyakov , linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org, linux-input@vger.kernel.org, netdev@vger.kernel.org, linux-rtc@vger.kernel.org, linux-serial@vger.kernel.org Subject: Re: [PATCH v4 7/9] mfd: ioc3: Add driver for SGI IOC3 chip Message-ID: <20190812125202.46608b74@cakuba.netronome.com> In-Reply-To: <20190811093212.88635fb1a6c796a073ec71ff@suse.de> References: <20190809103235.16338-1-tbogendoerfer@suse.de> <20190809103235.16338-8-tbogendoerfer@suse.de> <20190809142222.4558691e@cakuba.netronome.com> <20190811093212.88635fb1a6c796a073ec71ff@suse.de> Organization: Netronome Systems, Ltd. MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 11 Aug 2019 09:32:12 +0200, Thomas Bogendoerfer wrote: > > Also please don't use stdint types in the kernel, please try checkpatch > > to catch coding style issues. > > my patch already reduces them and checkpatch only warns about usage of printk > for the network part. Changing that to dev_warn/dev_err in the mfd patch didn't > seem the right thing to do. As I'm splitting the conversion patch into a few > steps I could also replace the printks. Thanks for looking into it. I was referring to the use of uint32_t instead of u32. Perhaps checkpatch has to be motivated with the --strict option to point those out?