Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2779388imu; Mon, 17 Dec 2018 07:42:26 -0800 (PST) X-Google-Smtp-Source: AFSGD/UrnWY/SebQed3jI55o6p7a1Gk8ZU44iMhQ9lABJPSNc2T/4gRuXXRIz43HbW9gk+Gzxpu7 X-Received: by 2002:a65:4142:: with SMTP id x2mr12231582pgp.356.1545061346237; Mon, 17 Dec 2018 07:42:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545061346; cv=none; d=google.com; s=arc-20160816; b=TUKHiCcZVhSsI+nYaNnABFsJhXP5TeNwaI/jybaA4b7rpvFfcyrg/kX0iMSHMXkLkT TYoDEHHDH0LRxoYQV66WXY5Fk6QhvDLEsMITAVyuydh2AN3EHzX81wB8Oe3ZOVLysPzR e0koEJ74TYGQH4N9AnbWIULdIzZr7nJSU0uyhSbkYEXeWPOfMdTwlmS3O/apWDKBKzDy X3HskjhkkJ0tSgcPsa3pMxrWqB1XJc6PEeLPgPJSR82yldV4pZPw3tprkwOeSMDLp5Of IMu0Zc8/qkQ/TonAYfXuDxFLayzFRet/sITx0pLspYsICkTQu3OVa54+UVkCDCH5pcuO Wx6g== 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:date:from:dkim-signature; bh=HtzbcogXkn682rdMDuWIbGFkOdQutURvhNqQPBQ8O5s=; b=tIFZkFC84Q//kJNNVbrUYI8JCSS2hI+z1srrstU0HBzmVClpX1UI31HdMfotakbsMA h4zNLgjPlLHZu71ID+bCUqQoaGxzLAOSw7ViGqwJutPlsVP+ZbOM9TFJBWMuf1yth+tI bmme3yi3/usxEbjx5a2fZUzBIdl76zUylwpnRMNZmHLsc9KJmi4VzpID799JVVU4gOkq dp55KseSwz3AIOKiu0p0C0WMv1X4a3K90y1SyuVKtHKkjq4zA37J1hFFKr7JmTAGaWfy EXslPTyDi+DPTePmaHB8ILoHBdFe8QBgCeP7uOqphxW6WiHadyea9YQHO3ePzq3sONYb UlhA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b="dOAt/Oks"; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 63si11031396pla.65.2018.12.17.07.42.11; Mon, 17 Dec 2018 07:42:26 -0800 (PST) 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; dkim=pass header.i=@gmail.com header.s=20161025 header.b="dOAt/Oks"; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387601AbeLQPlB (ORCPT + 99 others); Mon, 17 Dec 2018 10:41:01 -0500 Received: from mail-pg1-f196.google.com ([209.85.215.196]:46626 "EHLO mail-pg1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727798AbeLQPlB (ORCPT ); Mon, 17 Dec 2018 10:41:01 -0500 Received: by mail-pg1-f196.google.com with SMTP id w7so6278445pgp.13 for ; Mon, 17 Dec 2018 07:41:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=HtzbcogXkn682rdMDuWIbGFkOdQutURvhNqQPBQ8O5s=; b=dOAt/Oks50Yun0A1UFtcQn9emktvZee9bL/6Ml4rLqDRaiMBQZMvQjJWJx+FaECP4b x+058dZVHQo27Dxxbtrz0oSIGHQqqYU9dfM7JbGyf35NeArURiOxYIOIswrszb/5jEkG jd7JyBNzTOW5+v33vNqnHKhM5UC0mIUzyo8NUd1nN+uvTJ21BAT++tCAV/0ab8tKPwoy NcSgST1wGDZUf0ggICORx3bjq3UYSAPZSm4Wy2Pj/ELQzFITOrFlh7sr0sIj54DWoHGi YmghP3pzZ71rnJASSN9VWQJs6GDRPtWFeigi5rLKHeyRhP3gCs3PEiOF6YHOAzptb1fa +fsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=HtzbcogXkn682rdMDuWIbGFkOdQutURvhNqQPBQ8O5s=; b=gqb2BF85pUrEvJBZfYAbHiN/V4Izh//vslTh8SSmlZyMcaX74X9ozDBIHO6AyhdivD rPB9gXDuPLE2jvz6ZlNR1n3Zgp6lK5WIxGZrhbknDuYbzDUJ+4M/BAuoIOWtKFqXR0lZ x1jomdz553/vOelcJ0wj+y0OV/LOgt7zt+Vyjt3oYcgUN/4rnooH6XrrBQSWfB5Gwn4r 9H+B36fEE/K1CJg9o1bIh0zQekuCxqG1iO0btl1qc91iEFS/4MM63YcLXYQTEiZlYMs9 8RPh3RqyG/8LL0GLd476wJYNHkmNRq2drztdUfTkWLEzPv4ZF6DIpDGifOFBTCN3cDZ6 ha1Q== X-Gm-Message-State: AA+aEWY97k4zIcFPssGFVEn38HNmbqkCgb6u3r2BTJYO2ZZmW8BpnJGZ BXKe3u+acFfkhRPt61cAdnU= X-Received: by 2002:a63:1258:: with SMTP id 24mr12430982pgs.114.1545061260119; Mon, 17 Dec 2018 07:41:00 -0800 (PST) Received: from localhost ([121.137.63.184]) by smtp.gmail.com with ESMTPSA id h8sm18528356pfo.162.2018.12.17.07.40.58 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 17 Dec 2018 07:40:59 -0800 (PST) From: Sergey Senozhatsky X-Google-Original-From: Sergey Senozhatsky Date: Tue, 18 Dec 2018 00:40:56 +0900 To: Petr Mladek Cc: Sergey Senozhatsky , Tetsuo Handa , Dmitry Vyukov , Sergey Senozhatsky , Steven Rostedt , Linus Torvalds , Andrew Morton , LKML , syzkaller Subject: Re: [PATCH] printk: Add caller information to printk() output. Message-ID: <20181217154056.GA515@tigerII.localdomain> References: <20181203150603.cdqii263e4kmmibo@pathway.suse.cz> <20181204152724.ypk44mi4a56nrud4@pathway.suse.cz> <459018db-763b-9520-ead2-2c0d5975fbf3@i-love.sakura.ne.jp> <20181210130930.bas4fozjhe3dc5nu@pathway.suse.cz> <20181213121847.mwlr2vyv6qzclhk6@pathway.suse.cz> <20181213124255.GB3053@tigerII.localdomain> <20181217145452.3kev4rmo2l5lt2qy@pathway.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181217145452.3kev4rmo2l5lt2qy@pathway.suse.cz> User-Agent: Mutt/1.11.1 (2018-12-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (12/17/18 15:54), Petr Mladek wrote: > Now, I always felt that the "from" name was a bit strange but > nothing better came to my mind until today. Could be printk_caller, could be printk_origin. I don't have strong preferences. > I would like to rename "from" to "caller", see the patch below. > If you agree, I could push it on top or I could even squash it > into the original patch. Can we please squash or, better yet, ask Tetsuo to resend a new, renamed version? An immediate follow up patch that completely renames a just added feature feels like as if we failed to communicate it the usual way. -ss