From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751991AbdHBScO (ORCPT ); Wed, 2 Aug 2017 14:32:14 -0400 Received: from mail.kernel.org ([198.145.29.99]:56044 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751154AbdHBScM (ORCPT ); Wed, 2 Aug 2017 14:32:12 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0231D22BE4 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=acme@kernel.org Date: Wed, 2 Aug 2017 15:32:08 -0300 From: Arnaldo Carvalho de Melo To: "Michael S. Tsirkin" Cc: Ingo Molnar , linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, Adrian Hunter , David Ahern , Jason Wang , Jiri Olsa , Namhyung Kim , Wang Nan Subject: Re: [PATCH 16/18] tools include uapi: Grab a copy of linux/vhost.h Message-ID: <20170802183208.GI12201@kernel.org> References: <20170801195645.16986-1-acme@kernel.org> <20170801195645.16986-17-acme@kernel.org> <20170802001802-mutt-send-email-mst@kernel.org> <20170802141837.GG12201@kernel.org> <20170802184245-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170802184245-mutt-send-email-mst@kernel.org> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.8.3 (2017-05-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Wed, Aug 02, 2017 at 06:44:14PM +0300, Michael S. Tsirkin escreveu: > On Wed, Aug 02, 2017 at 11:18:37AM -0300, Arnaldo Carvalho de Melo wrote: > > Em Wed, Aug 02, 2017 at 12:19:18AM +0300, Michael S. Tsirkin escreveu: > > > On Tue, Aug 01, 2017 at 04:56:43PM -0300, Arnaldo Carvalho de Melo wrote: > > > > We will use it to generate tables for beautifying ioctl's 'cmd' arg. > > > Is this what tools/perf always does? Isn't there a way > > > to reuse the single header? > > So, that is how we did it at first, we tried to use files from the > > kernel from tools/ directly, and it worked most of the time. > > Shortest summary: We don't want to add to the workload of kernel > > developers, they don't have to care about tools/, if they don't want to. > OK then, thanks for the explanation. But if you want to, feel right at home! 8-) - Arnaldo