Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3842934yba; Mon, 29 Apr 2019 09:23:33 -0700 (PDT) X-Google-Smtp-Source: APXvYqzsc3mKy+0gRdxmx0yoVgfFimVp+qEmeWtdv33DGWvWQVd/Dv9oDtR8Fls6JRBxel+WtGhA X-Received: by 2002:a17:902:7284:: with SMTP id d4mr4621486pll.249.1556555013536; Mon, 29 Apr 2019 09:23:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556555013; cv=none; d=google.com; s=arc-20160816; b=qktxQwuYueBCJ1vUQa1CgQEvR/zOkOY+3aFKz7OJo86sYOSl5n0TvxjxRjX/sK5lpA 7ErI/jSBgRbTUWAKtYHgESIA8pIJxWSBX5fXRDiZbv084YM6lyCXWTekjhAYWZhTUqI+ HMkjuh83/dLDz/F6fiKB3fuNfdMxmovNacFVd6BYYTyNwQnG4ipIeYlvsWGhfOgYM/+1 lVVemNdgqVIJuGQcLTHY7VNw4g2mH3ItplqBXt1VF8uDenI8KArpQmhe2uCScPRRDiOZ oz0azkwcEQTJ5x0VpvKHi+DLfPYFW8bp4R3kvEIk51A85OkEm3UIBQzjtD+h01fluJ3T H7og== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:organization:from:references:cc:to:subject; bh=z1NytuXKebWf+nBTrVpmL3Hv0ZbVxFaioUajl36elJI=; b=xLX4xhzWjh6BnR4QbAS4tZr1emrFlpxrQhn9Uuhvx8p/fZq1ma760zJikTux8yrojH g+AhWzYy1pMXKeKsWCRAVorzIAN5Fwtaww8PTDj84TDDVHMlTlwPNrV+38yQCmzDwS6O KEkBDir/5w7nUvyhjz7s8NcwFBXzZkLVTOnwQ2+QZhH81k0elG0AHaCsUcTO03dJEoqc O5l2Yk6ZDYcG6qu8pFZWOb7ScilOlEZ005kMYg5j6tuassZfqypHaHn+NZy49ipagqQK IZ1jBYYJlfli3ZsyKXcjCjXkND/68YHtA2nH+w8lu9nxnHKd9zWfuY8qH8ijl4Aizf2w +0kg== ARC-Authentication-Results: i=1; mx.google.com; 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 t5si15887353plo.41.2019.04.29.09.23.17; Mon, 29 Apr 2019 09:23:33 -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; 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 S1728760AbfD2QVI (ORCPT + 99 others); Mon, 29 Apr 2019 12:21:08 -0400 Received: from mout.kundenserver.de ([212.227.17.13]:51893 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728518AbfD2QVI (ORCPT ); Mon, 29 Apr 2019 12:21:08 -0400 Received: from [192.168.1.110] ([77.9.18.117]) by mrelayeu.kundenserver.de (mreue108 [212.227.15.183]) with ESMTPSA (Nemesis) id 1Mwwm5-1gaMFo1KN1-00yOxX; Mon, 29 Apr 2019 18:20:39 +0200 Subject: Re: [PATCH 22/41] drivers: tty: serial: cpm_uart: fix logging calls To: Christophe Leroy , "Enrico Weigelt, metux IT consult" , linux-kernel@vger.kernel.org Cc: lorenzo.pieralisi@arm.com, linux-ia64@vger.kernel.org, linux-serial@vger.kernel.org, andrew@aj.id.au, gregkh@linuxfoundation.org, sudeep.holla@arm.com, liviu.dudau@arm.com, linux-mips@vger.kernel.org, vz@mleia.com, linux@prisktech.co.nz, sparclinux@vger.kernel.org, khilman@baylibre.com, macro@linux-mips.org, slemieux.tyco@gmail.com, matthias.bgg@gmail.com, jacmet@sunsite.dk, linux-amlogic@lists.infradead.org, andriy.shevchenko@linux.intel.com, linuxppc-dev@lists.ozlabs.org, davem@davemloft.net References: <1556369542-13247-1-git-send-email-info@metux.net> <1556369542-13247-23-git-send-email-info@metux.net> From: "Enrico Weigelt, metux IT consult" Organization: metux IT consult Message-ID: Date: Mon, 29 Apr 2019 18:20:31 +0200 User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:tyjLH/89kE1DHJTcj7yQUi5/jAAZ5RWHEAZ1BEYsF/kWEbRkhEH ZeaoyF1df0iBCTPcuY9nMjeSr96B+reEDpUpVACuMx58hYfg0Ovl49rQYub23PLjPK+yUID slNmJJYsTtoV+aOWQj1HRbA5ynpZ744EoI0A3tjgNZt1lZntfjDIcPBJU9Pfhs6+X+GK7WP t2o2PeOOqkzRGtr61EECg== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:VjVnj6n6CTk=:oLoFfSXyDvVj4bcXT6Ih/4 kL0M02IkYcM23hQBqWuWitHhRHbYjCdwo7yZCm+3pBB5no8X/Ztr8zkGyrVRrPMSlNYX0gK3B zLkvJlnWomR5UquIKZ13gZBV4/wjOl1kSv+4LiRfmqDVFOKnXIw+UAnjDoRPwbvqi2dxuhVHa IXOpQP00pNeser50seIPI/ovlbFbXJMBOVj1rt+0+0uSk0wstKhVVSaWsva/3NcMpYr44iwKN pL8XlLZaS2QOBl/ynF7SoVxFIvZnEMQhJorItjLuphNxXCvtzj8rhqLrrkkajgQ/0pjUy4Tiq 3WJvabYmjDHm85gs3l1RGTIP/leL/aifhMaOXM4Qx1sHVTJJxlMw1it7I31wrFqe0C0T5Tnk3 +5c0iqDZF6VBw0XsN+FMTdvwwN5so9je+rNUHID3sD5Yvm8xjw93Uo6bviA4/IiHvX0mEdSAj xKxitSG92ozPUuigbzb+oogChLmFoFbXi6s3ER6JiRSVDa9POQO26X1cecixkOz2/SyaNrtd5 wi3bBiZX/zwK/cEVJZg0BMo3ilxjtajTeiY2OsNJmCcBp61mptn8TueHekBXTEmqhyvIWEcks Pwcb//riDg9W1mzMTxm5SPvVgmRR3xYRVRFYmTDZ46n62kPQaVUbket7jbv2AqHlWLKiCqkR4 n4RNCb4xflN9afHD65/ruEWM68k3MVK9H9CPTVyg90priPsyjBaWTOwBYdw4mnSSnWx3W9pFV HxWHJkWswPIQsZuk5ib+4UBHe5duPTXhYEDd7bKV8coJopag7yNzn+KUAT2H9z/JPgKcId2QY fg2wigxSa7xJUSvPOamObTx2eMiO5lok3NOq7YtNTSlPbcGNlc13ID61c5JH/6t6NJ6lPjs Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 29.04.19 17:59, Christophe Leroy wrote: > If we want to do something useful, wouldn't it make more sense to > introduce the use of dev_err() in order to identify the faulting device > in the message ? Well, I could get the struct device* pointer via pinfo.port->dev, but I wasn't entirely sure that it's always defined before these functions could be called. Shall I change it to dev_*() ? --mtx -- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering info@metux.net -- +49-151-27565287