Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752907AbbBXJHu (ORCPT ); Tue, 24 Feb 2015 04:07:50 -0500 Received: from mail-we0-f172.google.com ([74.125.82.172]:36375 "EHLO mail-we0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750880AbbBXJHr (ORCPT ); Tue, 24 Feb 2015 04:07:47 -0500 Date: Tue, 24 Feb 2015 10:07:43 +0100 From: Ingo Molnar To: Boaz Harrosh Cc: Ingo Molnar , Andy Lutomirski , Ross Zwisler , X86 ML , linux-kernel , "Roger C. Pao" , Dan Williams , Thomas Gleixner , Linus Torvalds , linux-nvdimm , "H. Peter Anvin" , Matthew Wilcox , Christoph Hellwig , Andrew Morton , Vivek Goyal Subject: Re: [PATCH 2/3 v3] resource: Add new flag IORESOURCE_MEM_WARN Message-ID: <20150224090742.GC19930@gmail.com> References: <54EB1D33.3050107@plexistor.com> <54EB206E.4010009@plexistor.com> <54EC38CA.6050607@plexistor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54EC38CA.6050607@plexistor.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: 949 Lines: 31 * Boaz Harrosh wrote: > --- a/kernel/resource.c > +++ b/kernel/resource.c > @@ -1075,8 +1075,13 @@ struct resource * __request_region(struct resource *parent, > break; > if (conflict != parent) { > parent = conflict; > - if (!(conflict->flags & IORESOURCE_BUSY)) > + if (!(conflict->flags & IORESOURCE_BUSY)) { > + if (conflict->flags & IORESOURCE_MEM_WARN) > + pr_warn("request unknown region [mem %#010llx-%#010llx] %s\n", > + conflict->start, conflict->end, > + conflict->name); Maybe: 'request region with unknown memory type [mem ...]'? The driver (we hope!) very well knows about the region so it's not totally unknown. Thanks, Ingo -- 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/