Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751126Ab3CWKF0 (ORCPT ); Sat, 23 Mar 2013 06:05:26 -0400 Received: from smtp-out-087.synserver.de ([212.40.185.87]:1074 "EHLO smtp-out-087.synserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750733Ab3CWKFZ (ORCPT ); Sat, 23 Mar 2013 06:05:25 -0400 X-SynServer-TrustedSrc: 1 X-SynServer-AuthUser: lars@metafoo.de X-SynServer-PPID: 25369 Message-ID: <514D7ED4.2030205@metafoo.de> Date: Sat, 23 Mar 2013 11:07:16 +0100 From: Lars-Peter Clausen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 MIME-Version: 1.0 To: Sebastian Hesselbarth CC: Grant Likely , Rob Herring , Rob Landley , Mike Turquette , Stephen Warren , Thierry Reding , Dom Cobley , Linus Walleij , Arnd Bergmann , Andrew Morton , Russell King - ARM Linux , Rabeeh Khoury , Daniel Mack , Jean-Francois Moine , devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v3] clk: add si5351 i2c common clock driver References: <1360414772-12232-1-git-send-email-sebastian.hesselbarth@gmail.com> <1363603397-2762-1-git-send-email-sebastian.hesselbarth@gmail.com> <514B4CBF.7070106@metafoo.de> <514B7C80.2070008@gmail.com> In-Reply-To: <514B7C80.2070008@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1028 Lines: 23 On 03/21/2013 10:32 PM, Sebastian Hesselbarth wrote: >>> + >>> + dev_info(&client->dev, "registered si5351 i2c client\n"); >>> + >> >> That's just noise, imagine every driver would print such a line, your bootlog >> would be scrolling for hours ;) I'd either remove it or make it dev_dbg > > Actually, I understand not to have it, but if you don't want it you can still > boot with "quiet", can't you? Having one single line that helps you see it has > been probed helps a lot. But, I don't have a strong opinion on that and can > make it dev_dbg. It is useful during development, but in my opinion only as long as not every other driver does this as well. If you want to check whether a device has been probed you can easily do this by checking the drivers sysfs node. - Lars -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/