From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [PATCH 02/10] tooling headers: Synchronize updated s390 kvm UAPI headers Date: Tue, 6 Feb 2018 11:53:10 +0100 Message-ID: <20180206105310.2hi7mjqwu6tkm3lx@gmail.com> References: <20180205195620.9010-1-acme@kernel.org> <20180205195620.9010-3-acme@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-wm0-f65.google.com ([74.125.82.65]:36503 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752246AbeBFKxP (ORCPT ); Tue, 6 Feb 2018 05:53:15 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-perf-users-owner@vger.kernel.org List-ID: To: Christian Borntraeger Cc: Arnaldo Carvalho de Melo , linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, Arnaldo Carvalho de Melo , Adrian Hunter , David Ahern , Jiri Olsa , Namhyung Kim , Radim =?utf-8?B?S3LEjW3DocWZ?= , Wang Nan , Paolo Bonzini * Christian Borntraeger wrote: > Arnaldo > > what is the proposed way of forwarding kvm uapi changes to the perf copy? > Are you going to detect and fixup that yourself? Do you want to be notified? > Or do you even want to have a patch? Yes, that's the normal flow: you can just ignore any warnings, we are syncing the headers up at around -rc1. (Many of them are already synced up.) I.e. there's no constraint on kernel development and there's no need for you to deal with tooling details. Thanks, Ingo