Received: by 10.223.176.46 with SMTP id f43csp77101wra; Fri, 19 Jan 2018 14:04:38 -0800 (PST) X-Google-Smtp-Source: ACJfBos+1jtL4MhpEJuR6cSohjrPIxgo8x93LLF578HmMUzgwrsR1o8/5Qm5xn7OfyP46lyCuJXu X-Received: by 10.98.60.132 with SMTP id b4mr44172017pfk.120.1516399478282; Fri, 19 Jan 2018 14:04:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516399478; cv=none; d=google.com; s=arc-20160816; b=DbhE8Uc3ZirTucVF7TKVIkdjggdP5CPk3664yKNdHWMf/qqrZKNtUP12Fd1Ox4Gg81 XYXNZjU8j9aGp9GMaye3YFa+/+t+Yz/7gd6yWq1/RsWUI3skTJZQne2zFGOHPFWyBbp0 nk8vd1n1gJfPzEkrJlx63ZQkwid0J3cdaN44ISGPlpuoBQtjG0W0U9SLQET7XB/1CDr6 qrkGRp/npObun1GirJrjLQoGRptejtUPVEOvV2kTybN5pYZV99HVfxP2aIPkI34rmE/q WZb3yzCtV+QhhIz7whNzBzRyKn+cAmIOirVcjhwClF2Kb9BiObCgPLcxijTyFTZmv6co DxkQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dmarc-filter:arc-authentication-results; bh=7Am+MdYWCiTC5QNZijNMVgoB5L65I0dqgbfUkTV4g5w=; b=MpRwplfoPkpk6YR6Bt91clX8nbC3ZW6d5UkngrgBui0aeFgMafHOhViccW+wXS954O j63M2Lj+BGRMEt1CXcpYHLv7FxZg3F6FRSZPCWNkmcrmAv0IcLgUztuzFWz+TtHkGzYt ZZ26gyfSa2iWOiA0f7wPENYr4h9fOY08xqbgYlguZJv5TUPdvcS62w6eNKNSW1whO14W KtPYVB//AZbbWzf9l4AnVj4YEG+7VU88zGjn4jdqwh8J4YTG4/S36E8zTujlMQYAYdBd o6JGRLieFRwp3NlXdIb02te5BYt28MLIagbXjJzqzoursRk33ps1Sh1NuLEGAQljEwbu xKbw== 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 q16-v6si1121802pls.524.2018.01.19.14.04.23; Fri, 19 Jan 2018 14:04:38 -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; 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 S1756626AbeASWCm (ORCPT + 99 others); Fri, 19 Jan 2018 17:02:42 -0500 Received: from mail.kernel.org ([198.145.29.99]:42888 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756492AbeASWCf (ORCPT ); Fri, 19 Jan 2018 17:02:35 -0500 Received: from gandalf.local.home (cpe-172-100-180-131.stny.res.rr.com [172.100.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 6089620853; Fri, 19 Jan 2018 22:02:34 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6089620853 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org Date: Fri, 19 Jan 2018 17:02:32 -0500 From: Steven Rostedt To: "Vladislav Valtchev (VMware)" Cc: linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org, y.karadz@gmail.com Subject: Re: [PATCH v4 1/3] trace-cmd: Make read_proc() to return int status via OUT arg Message-ID: <20180119170232.4da3f768@gandalf.local.home> In-Reply-To: <20180119165802.19daee80@gandalf.local.home> References: <20180116195343.12800-1-vladislav.valtchev@gmail.com> <20180116195343.12800-2-vladislav.valtchev@gmail.com> <20180119165802.19daee80@gandalf.local.home> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 19 Jan 2018 16:58:02 -0500 Steven Rostedt wrote: > Just to let you know. I accepted all three of your patches. I have one > comment, (and changed this myself). Anyway, Great job so far! I think I'm all set to start getting trace-cmd 2.7 out now. Unfortunately, I don't think I'll be able to get to that before I leave on my next trip. -- Steve