[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110520115614.GH14745@elte.hu>
Date: Fri, 20 May 2011 13:56:14 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Huang Ying <ying.huang@...el.com>
Cc: Len Brown <lenb@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andi Kleen <andi@...stfloor.org>,
"Luck, Tony" <tony.luck@...el.com>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
Andi Kleen <ak@...ux.intel.com>,
"Wu, Fengguang" <fengguang.wu@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH 5/9] HWPoison: add memory_failure_queue()
* Huang Ying <ying.huang@...el.com> wrote:
> > So why are we not working towards integrating this into our event
> > reporting/handling framework, as i suggested it from day one on when you
> > started posting these patches?
>
> The memory_failure_queue() introduced in this patch is general, that is, it
> can be used not only by ACPI/APEI, but also any other hardware error
> handlers, including your event reporting/handling framework.
Well, the bit you are steadfastly ignoring is what i have made clear well
before you started adding these facilities: THEY ALREADY EXISTS to a large
degree :-)
So you were and are duplicating code instead of using and extending existing
event processing facilities. It does not matter one little bit that the code
you added is partly 'generic', it's still overlapping and duplicated.
Thanks,
Ingo
--
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