From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <54EC39EB.8030901@plexistor.com> Date: Tue, 24 Feb 2015 10:44:27 +0200 From: Boaz Harrosh MIME-Version: 1.0 Subject: Re: [PATCH 2/3 v3] resource: Add new flag IORESOURCE_MEM_WARN References: <54EB1D33.3050107@plexistor.com> <54EB206E.4010009@plexistor.com> <54EC38CA.6050607@plexistor.com> In-Reply-To: <54EC38CA.6050607@plexistor.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org To: Ingo Molnar Cc: 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 List-ID: On 02/24/2015 10:39 AM, Boaz Harrosh wrote: > > Resource providers set this flag if they want > that request_region_XXX will print a warning in dmesg > if this particular resource is locked by a driver. > > Thous acting as a Protocol Police about experimental > devices that did not pass a comity approval. > > The Only user of this flag is x86/kernel/e820.c that > wants to WARN about UNKNOWN memory types. > Hi Ingo So I slept on it and I think this simple version is safe and does what we need. It is more simple than the wrappers thing Who can push such a patch, can you push it through your tree or is there another maintainer that needs to push this? Who can we ask about the safeness of these flags? > Signed-off-by: Boaz Harrosh <> Thanks Boaz