Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750946AbbLCSk7 (ORCPT ); Thu, 3 Dec 2015 13:40:59 -0500 Received: from mail.skyhub.de ([78.46.96.112]:38557 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750873AbbLCSk5 (ORCPT ); Thu, 3 Dec 2015 13:40:57 -0500 Date: Thu, 3 Dec 2015 19:40:51 +0100 From: Borislav Petkov To: Toshi Kani Cc: Linus Torvalds , Dan Williams , Andrew Morton , "Rafael J. Wysocki" , Tony Luck , Vishal L Verma , Linux MM , "linux-nvdimm@lists.01.org" , Linux ACPI , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v3 1/3] resource: Add @flags to region_intersects() Message-ID: <20151203184051.GE3213@pd.tnic> References: <1448404418-28800-1-git-send-email-toshi.kani@hpe.com> <1448404418-28800-2-git-send-email-toshi.kani@hpe.com> <20151201135000.GB4341@pd.tnic> <20151201171322.GD4341@pd.tnic> <1449168859.9855.54.camel@hpe.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1449168859.9855.54.camel@hpe.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 908 Lines: 24 On Thu, Dec 03, 2015 at 11:54:19AM -0700, Toshi Kani wrote: > Adding a new type for regular memory will require inspecting the codes > using IORESOURCE_MEM currently, and modify them to use the new type if > their target ranges are regular memory. There are many references to this > type across multiple architectures and drivers, which make this inspection > and testing challenging. What's wrong with adding a new type_flags to struct resource and not touching IORESOURCE_* at all? They'll be called something like RES_TYPE_RAM, _PMEM, _SYSMEM... Or would that confuse more...? -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/