From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754479AbbB0ACk (ORCPT ); Thu, 26 Feb 2015 19:02:40 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:44765 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753539AbbB0ACj (ORCPT ); Thu, 26 Feb 2015 19:02:39 -0500 Message-ID: <54EFB41B.4050309@codeaurora.org> Date: Thu, 26 Feb 2015 16:02:35 -0800 From: Stephen Boyd User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Geert Uytterhoeven , Jonathan Corbet , Andrew Morton , Mike Turquette CC: Tetsuo Handa , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Geert Uytterhoeven Subject: Re: [PATCH 0/3] lib/vsprintf: Doc improvements and clock support References: <1424949183-31425-1-git-send-email-geert@linux-m68k.org> In-Reply-To: <1424949183-31425-1-git-send-email-geert@linux-m68k.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/26/15 03:13, Geert Uytterhoeven wrote: > From: Geert Uytterhoeven > > Hi, > > This patch series improves the documentation for printk() formats, and > adds support for printing clocks. The latter has always been a hassle if > you wanted to support both the common and legacy clock frameworks. Would the hassle go away if everyone moved to the common framework? I'm mostly trying to understand the justification. Also, I wonder why we wouldn't want to add formats for all the other handle based frameworks that we have nowdays (gpio, regulator, pinctrl, etc.). -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project