Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp493341imm; Fri, 1 Jun 2018 04:48:43 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLSCZbgK7qcuoSIE7LqnOZJsNi6Z9yN9EVG6WyjmgC36yd5hFJyU/XI1+QB76wAFJAErDL7 X-Received: by 2002:a63:648:: with SMTP id 69-v6mr8657799pgg.205.1527853723642; Fri, 01 Jun 2018 04:48:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527853723; cv=none; d=google.com; s=arc-20160816; b=vH/0F1A6NgyRFV8eML6B8+A/5xq0pXlSA+qikXOlJGQpiZzSLdRZIbEVe+MNTWLRa7 W/ra+Wu8lZuBK+/K8xD0/XUDX4CwICLAC9Bs4ly6NWJhXlgGJ4FjgPAN0cD6yl0FyUpl LLH7yaQthZjiMt7nFZFsUXVyaDqdcTQ/pa8ppCxbNz/AmNXxft1d2ICxriE7/gmChAPb sVaMu2rlZ9zcygZWiwcHgk6AjElH4k+gDqO02zB9JdtObRtoBRqd/qXMSmY7/CtD8Ign 1he5X2ihihWNk/4ERTDeSW3dAxgjYJaEvQRTj5QLBp9u00L3RyuRPzE9kYyBtJHPyERZ R71g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=ekOwtYJb72KXMT90Mg1ju1vVXIKnPFlsPKCamw4gUc4=; b=s4e1fro6hQlQEJkJQskfBUmrZPyKF69bpIFzqO9IgxAwDGn7SYBWxKRaEHKR+Ch/Lb GRgUkBjfyeExzr7aFMoa16VqdCxYJHT4s2ljKNouMFO2b+W8BoeXDmolZPHbp4Fwe3kw lHL4fYVYTTq8mBUTzeoGjd8t2JjK4PdzEU02tPOFJeLMdYxDgXkrRwM08jCq+THzCEF7 zwq+LSWmK9OvC2zT6xBkFusopbKprxKdeAACdaKdrYgRlzGwMwhp0RLie1KSvya805Ci I4uizHR3bTUlb2oOonnXx1ZT2nRoCU75mRKTidol8meNm4b8+t0LMVIlB6gX06a265LU tRQA== 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 d7-v6si40660438pfe.214.2018.06.01.04.48.29; Fri, 01 Jun 2018 04:48:43 -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 S1751806AbeFALro (ORCPT + 99 others); Fri, 1 Jun 2018 07:47:44 -0400 Received: from mx2.suse.de ([195.135.220.15]:58364 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751012AbeFALrm (ORCPT ); Fri, 1 Jun 2018 07:47:42 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext-too.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id C9955AE54; Fri, 1 Jun 2018 11:47:39 +0000 (UTC) Date: Fri, 1 Jun 2018 13:47:38 +0200 From: Petr Mladek To: Linus Torvalds Cc: Geert Uytterhoeven , baijiaju1990@gmail.com, Jonathan Corbet , Michael Turquette , sboyd@kernel.org, Zhang Rui , Eduardo Valentin , Eric Anholt , Stefan Wahren , Greg Kroah-Hartman , Sergey Senozhatsky , Steven Rostedt , "open list:DOCUMENTATION" , linux-clk@vger.kernel.org, Linux PM , linux-serial , linux-arm-kernel , Linux-Renesas , Linux Kernel Mailing List Subject: Re: [PATCH 0/4] lib/vsprintf: Remove atomic-unsafe support for printk format %pCr Message-ID: <20180601114738.kdoggkha2yosjgbv@pathway.suse.cz> References: <1527845302-12159-1-git-send-email-geert+renesas@glider.be> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170421 (1.8.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 2018-06-01 06:00:47, Linus Torvalds wrote: > On Fri, Jun 1, 2018 at 4:29 AM Geert Uytterhoeven > wrote: > > > > This patch series: > > - Changes all existing users of "%pCr" to print the result of > > clk_get_rate() directly, which is safe as they all do this in task > > context only, > > - Removes support for the "%pCr" printk format. > > Looks good to me. > > What tree will this go through? The normal printk one? Just checking > that this doesn't end up falling through the cracks because nobody > knows who would take it... I will take it via printk.git. There already is bunch of vsprintf changes for-4.18. Best Regards, Petr