Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.4 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AA89FC2D0A8 for ; Mon, 28 Sep 2020 08:30:29 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 37D2E2076B for ; Mon, 28 Sep 2020 08:30:27 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=suse.com header.i=@suse.com header.b="TnqNs9ou" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 37D2E2076B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=suse.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1kMoY2-0006g4-2g; Mon, 28 Sep 2020 08:30:14 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1kMoY1-0006fz-2O for xen-devel@lists.xenproject.org; Mon, 28 Sep 2020 08:30:13 +0000 X-Inumbo-ID: 91891997-a0a3-4694-906d-3c48426fa98e Received: from mx2.suse.de (unknown [195.135.220.15]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id 91891997-a0a3-4694-906d-3c48426fa98e; Mon, 28 Sep 2020 08:30:09 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1601281808; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=NU0tNlvjTbnSeKrR7JOCUI7g4zQZjnb03dLvE/STFWc=; b=TnqNs9ouNu8SXB5hmgKiJAOyW/SNJda1chs0c3R7nYoo2ory6BSyrIpvC9xjt/0138dHVB JO30jKd/BDPaoQXwJvoA6g9Hvp/9mDXaFtAzgXqAVvDJGBy1weC9KlE9Kn6iBs7aUWM7p2 SH2OpEHU711T96QcWEyr8gE9bsnpZ30= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 57E5BAC3C; Mon, 28 Sep 2020 08:30:08 +0000 (UTC) Subject: Ping: [PATCH 0/6] tools/include: adjustments to the population of xen/ From: Jan Beulich To: Ian Jackson , Wei Liu Cc: "xen-devel@lists.xenproject.org" References: <2a9f86aa-9104-8a45-cd21-72acd693f924@suse.com> Message-ID: Date: Mon, 28 Sep 2020 10:30:07 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: <2a9f86aa-9104-8a45-cd21-72acd693f924@suse.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: xen-devel@lists.xenproject.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" On 10.09.2020 14:09, Jan Beulich wrote: > While looking at what it would take to move around libelf/ > in the hypervisor subtree, I've run into this rule, which I > think can do with a few improvements and some simplification. > > 1: adjust population of acpi/ > 2: fix (drop) dependencies of when to populate xen/ > 3: adjust population of public headers into xen/ > 4: properly install Arm public headers > 5: adjust x86-specific population of xen/ > 6: drop remaining -f from ln invocations While Andrew did voice some objection to symlinking in general, in reply I've clarified I'm not up to the work involved to doing so in cleanly enough a way. I'd therefore like to ask that either this series be considered for putting in, or that it be made clear how else the issues addressed here are going to be dealt with (and by whom and when). Thanks, Jan