public inbox for linux-edac@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Aristeu Rozanski <aris@redhat.com>
Cc: linux-edac@vger.kernel.org, mchehab@kernel.org
Subject: Re: [PATCH] i5000_edac: mark as BROKEN
Date: Mon, 17 Oct 2022 16:41:20 +0200	[thread overview]
Message-ID: <Y01pkNgd4oegdk5r@zn.tnic> (raw)
In-Reply-To: <20220928124815.ta6k4jiiyy6diudr@redhat.com>

On Wed, Sep 28, 2022 at 08:48:15AM -0400, Aristeu Rozanski wrote:
> i5000_edac supports very old hardware which isn't available and it's
> been broken for single/dual channel for many years without anyone
> noticing. Marking as BROKEN.
> 
> Signed-off-by: Aristeu Rozanski <aris@redhat.com>
> 
> diff --git a/drivers/edac/Kconfig b/drivers/edac/Kconfig
> index 17562cf1fe97..e659e4712a25 100644
> --- a/drivers/edac/Kconfig
> +++ b/drivers/edac/Kconfig
> @@ -211,6 +211,7 @@ config EDAC_R82600
>  config EDAC_I5000
>  	tristate "Intel Greencreek/Blackford chipset"
>  	depends on X86 && PCI
> +	depends on BROKEN
>  	help
>  	  Support for error detection and correction the Intel
>  	  Greekcreek/Blackford chipsets.

Applied, thanks.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

      reply	other threads:[~2022-10-17 14:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 18:10 [RESEND PATCH] i5000_edac: fix slot number passed to determine_mtr() Aristeu Rozanski
2022-09-21 19:38 ` Borislav Petkov
2022-09-22 13:46   ` Aristeu Rozanski
2022-09-22 13:55     ` Borislav Petkov
2022-09-26 16:51       ` Aristeu Rozanski
2022-09-26 18:02         ` Borislav Petkov
2022-09-28 12:48           ` [PATCH] i5000_edac: mark as BROKEN Aristeu Rozanski
2022-10-17 14:41             ` Borislav Petkov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y01pkNgd4oegdk5r@zn.tnic \
    --to=bp@alien8.de \
    --cc=aris@redhat.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=mchehab@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox