| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <54EFB41B.4050309@codeaurora.org> Date: Thu, 26 Feb 2015 16:02:35 -0800 From: Stephen Boyd <sboyd@...eaurora.org> To: Geert Uytterhoeven <geert@...ux-m68k.org>, Jonathan Corbet <corbet@....net>, Andrew Morton <akpm@...ux-foundation.org>, Mike Turquette <mturquette@...aro.org> CC: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, Geert Uytterhoeven <geert+renesas@...der.be> Subject: Re: [PATCH 0/3] lib/vsprintf: Doc improvements and clock support On 02/26/15 03:13, Geert Uytterhoeven wrote: > From: Geert Uytterhoeven <geert+renesas@...der.be> > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists