[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54EC39EB.8030901@plexistor.com>
Date: Tue, 24 Feb 2015 10:44:27 +0200
From: Boaz Harrosh <boaz@...xistor.com>
To: Ingo Molnar <mingo@...hat.com>
CC: Andy Lutomirski <luto@...capital.net>,
Ross Zwisler <ross.zwisler@...ux.intel.com>,
X86 ML <x86@...nel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
"Roger C. Pao" <rcpao.enmotus@...il.com>,
Dan Williams <dan.j.williams@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-nvdimm <linux-nvdimm@...ts.01.org>,
"H. Peter Anvin" <hpa@...or.com>,
Matthew Wilcox <willy@...ux.intel.com>,
Christoph Hellwig <hch@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Vivek Goyal <vgoyal@...hat.com>
Subject: Re: [PATCH 2/3 v3] resource: Add new flag IORESOURCE_MEM_WARN
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 <boaz@...xistor.com>
<>
Thanks
Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists