Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp1903050ybc; Wed, 13 Nov 2019 06:10:48 -0800 (PST) X-Google-Smtp-Source: APXvYqx/DVtY4S29jPhB6a2nKWEJnakuLKGIFTK81jgjay2Oi36RuBXCx9I/uAto0Gci9quYBN/s X-Received: by 2002:a17:906:6043:: with SMTP id p3mr2911491ejj.103.1573654247777; Wed, 13 Nov 2019 06:10:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573654247; cv=none; d=google.com; s=arc-20160816; b=IAcaP1Zm6uZvM6HO99msGlyBcxuG3K3Lwe4RCnsLell3RtPeYGfKsJepNo8HPlWIJ2 v5zEPNFH6/fSvetDfa9zq4ri9eBcOjoph2TEfC0CBQrVF3MCUY3nqCepKfsGHHg6BDbD jKfP3niOuHoeqk0U3vx1x9Nx/4LQdRqrHZN/MP5u5pWo9AoJENTtesxmIHrg96kbgz47 Mo2ajzgEeIJBf64DkTY2VLgbFrcYybKg9DO29j1xvqruN6hkF4AIpmxBV6Pa8tSBqxDR rEdPq6ktOSv+ULMLY162Xtl1G0eNBGaufz9V4INxT5AVTAfbtHyXFmueYfrI9k7O0Y9U Rn4w== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=WkOMxVjqALlRgLxJ30zM8zIn7kwvaqJLuKuuFaWeu4k=; b=hZQ2rKnbjtwm3V6jFpFmLXJ8fVinLzybd+rO+dHToCZ5Yqlch9TPKpcNJKaz4Ety+4 /9nZBg4rsId9hQRSgOh3HJSouOFTfsoAW2yjMGTRCHFxNWAhnQMCcaE6Sv7FdD2/SIWc ahQRWvYlJqjkdddoxzFPnPCImPRWUzFMF820cezs1oc+g8BcQMb+h/FYb9KhmttY7hwZ 5B1qccC8JngfkFjb9SUdaaq72R217Vg0WnIG1rWsJpwShEOl/rTMCN8zm2gwKld9V4Iq 1tAj8GqbmaFBI+J+LDDb099+Gt+HaDa68VizHJdi6eiDiFo9u4C3I/L0DpsaCdOmKR1E w4IQ== 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 y24si1303765edm.333.2019.11.13.06.10.22; Wed, 13 Nov 2019 06:10:47 -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 S1727540AbfKMOG2 (ORCPT + 99 others); Wed, 13 Nov 2019 09:06:28 -0500 Received: from mx2.suse.de ([195.135.220.15]:41908 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726410AbfKMOG1 (ORCPT ); Wed, 13 Nov 2019 09:06:27 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 63E00B211; Wed, 13 Nov 2019 14:06:26 +0000 (UTC) Subject: Re: [Xen-devel] [PATCH 3/3] xen/mcelog: also allow building for 32-bit kernels To: Jan Beulich , Boris Ostrovsky Cc: "xen-devel@lists.xenproject.org" , lkml References: <07358162-1d03-63f5-ad14-95a2e0e23018@suse.com> <4577bd33-e4b5-9869-3760-c55471382f01@suse.com> From: =?UTF-8?B?SsO8cmdlbiBHcm/Dnw==?= Message-ID: Date: Wed, 13 Nov 2019 15:06:25 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 MIME-Version: 1.0 In-Reply-To: <4577bd33-e4b5-9869-3760-c55471382f01@suse.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 13.11.19 14:47, Jan Beulich wrote: > On 13.11.2019 01:15, Boris Ostrovsky wrote: >> On 11/11/19 9:46 AM, Jan Beulich wrote: >>> There's no apparent reason why it can be used on 64-bit only. >>> >>> Signed-off-by: Jan Beulich >>> >>> --- a/drivers/xen/Kconfig >>> +++ b/drivers/xen/Kconfig >>> @@ -285,7 +285,7 @@ config XEN_ACPI_PROCESSOR >>> >>> config XEN_MCE_LOG >>> bool "Xen platform mcelog" >>> - depends on XEN_DOM0 && X86_64 && X86_MCE >>> + depends on XEN_DOM0 && X86 && X86_MCE >> >> Can we have X86_MCE without X86? > > I don't think we can. Is this a request to drop the middle > operand altogether? I think this would be reasonable. X86_64 was an additional dependency, while X86 isn't. With the X86 removed: Reviewed-by: Juergen Gross Juergen