From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com [209.85.218.41]) by kanga.kvack.org (Postfix) with ESMTP id 0D3B182F99 for ; Wed, 23 Dec 2015 21:23:59 -0500 (EST) Received: by mail-oi0-f41.google.com with SMTP id y66so132722276oig.0 for ; Wed, 23 Dec 2015 18:23:59 -0800 (PST) Received: from g4t3428.houston.hp.com (g4t3428.houston.hp.com. [15.201.208.56]) by mx.google.com with ESMTPS id i4si24376077oes.15.2015.12.23.18.23.58 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 23 Dec 2015 18:23:58 -0800 (PST) Message-ID: <1450923815.19330.4.camel@hpe.com> Subject: Re: [PATCH 01/11] resource: Add System RAM resource type From: Toshi Kani Date: Wed, 23 Dec 2015 19:23:35 -0700 In-Reply-To: <20151223142349.GG30213@pd.tnic> References: <20151216122642.GE29775@pd.tnic> <1450280642.29051.76.camel@hpe.com> <20151216154916.GF29775@pd.tnic> <1450283759.20148.11.camel@hpe.com> <20151216174523.GH29775@pd.tnic> <20151216181712.GJ29775@pd.tnic> <1450302758.20148.75.camel@hpe.com> <20151222113422.GE3728@pd.tnic> <1450814672.10450.83.camel@hpe.com> <20151223142349.GG30213@pd.tnic> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Borislav Petkov Cc: Dan Williams , Andrew Morton , linux-arch@vger.kernel.org, Linux MM , "linux-kernel@vger.kernel.org" , Linus Torvalds , "Rafael J. Wysocki" On Wed, 2015-12-23 at 15:23 +0100, Borislav Petkov wrote: > On Tue, Dec 22, 2015 at 01:04:32PM -0700, Toshi Kani wrote: : > > I agree that we can add new interfaces with the type check. This > > 'type' > > may need some clarification since it is an assigned type, which is > > different from I/O resource type. That is, "System RAM" is an I/O > > resource type (i.e. IORESOURCE_SYSTEM_RAM), but "Crash kernel" is an > > assigned type to a particular range of System RAM. A range may be > > associated with multiple names, so as multiple assigned types. For > > lack of a better idea, I may call it 'assign_type'. I am open for a > > better name. > > Or assigned_type or named_type or so... > > I think we should avoid calling it "type" completely in order to avoid > confusion with the IORESOURCE_* types and call it "desc" or so to mean > description, sort, etc, because the name is also a description of the > resource to a certain degree... Agreed. I will use 'desc'. > > OK, I will try to convert the existing callers with the new interfaces. > > Either that or add the new interfaces, use them in your use case, add > big fat comments explaining that people should use those from now on > when searching by name and add a check to checkpatch to catch future > mis-uses... Sounds good. I will look into it. Thanks, -Toshi -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org