From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C738AC54E4A for ; Mon, 11 May 2020 13:55:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A7F8E20736 for ; Mon, 11 May 2020 13:55:18 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alien8.de header.i=@alien8.de header.b="leKdjIe7" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730519AbgEKNzR (ORCPT ); Mon, 11 May 2020 09:55:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34196 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1730316AbgEKNzQ (ORCPT ); Mon, 11 May 2020 09:55:16 -0400 Received: from mail.skyhub.de (mail.skyhub.de [IPv6:2a01:4f8:190:11c2::b:1457]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 70300C061A0C for ; Mon, 11 May 2020 06:55:16 -0700 (PDT) Received: from zn.tnic (p200300EC2F05F10085E3BAC78343E356.dip0.t-ipconnect.de [IPv6:2003:ec:2f05:f100:85e3:bac7:8343:e356]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 57EC91EC031B; Mon, 11 May 2020 15:55:12 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1589205312; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=2qyWyjkfg5PL3c/zl1zN8QlpUrK52KyMAjLNKt6X7Sg=; b=leKdjIe7wgxA4KghUSA2SVFc1vGevmBndDY4j2Ttfuw937nMIm5VU9+E2BSGOt9LA3Jatf KP+3AYdU8GUAVQW28p+MWqDDL2uVtG5rmke1hkaulCcsICXGA9J9WX7UcRYLHWUEGuoCNO aD+Tlbt98EGYhUlp+p550gTJ0LK1224= Date: Mon, 11 May 2020 15:55:08 +0200 From: Borislav Petkov To: "Hawa, Hanna" Cc: "james.morse@arm.com" , Robert Richter , "linux-edac@vger.kernel.org" , "Woodhouse, David" , "Krupnik, Ronen" , talel@amazon.com, jonnyc@amazon.com, "Hanoch, Uri" Subject: Re: [RFC] Support different block names with same EDAC device Message-ID: <20200511135507.GC25861@zn.tnic> References: <0ae313a4-97c3-5681-f22c-23decb261b74@amazon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <0ae313a4-97c3-5681-f22c-23decb261b74@amazon.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-edac-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-edac@vger.kernel.org On Mon, May 11, 2020 at 03:59:38PM +0300, Hawa, Hanna wrote: > Can the edac device infrastructure support different block names? Shall we > add support for such feature? Does the "EDAC Blocks" section here: Documentation/driver-api/edac.rst answer your question? -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette