Linux EDAC development
 help / color / mirror / Atom feed
From: Tushar Tibude <tushar.tibude1000@gmail.com>
To: mchehab@kernel.org, bp@alien8.de, tony.luck@intel.com,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: qiuxu.zhuo@intel.com, Tushar Tibude <tushar.tibude1000@gmail.com>
Subject: [PATCH 0/3] EDAC: fix error reporting handling during init for
Date: Thu, 30 Apr 2026 14:12:20 +0530	[thread overview]
Message-ID: <20260430084223.9298-1-tushar.tibude1000@gmail.com> (raw)

For some drivers, during initialization error reporting is enabled,
but not properly handled during teardown or init fail, and this leaves 
it enabled in the register on exit.

This inconsistency was first identified for i7300_edac.c and a patch 
addressing it was reviewed: 

Link: https://lore.kernel.org/linux-edac/20260429094806.25097-1-tushar.tibude1000@gmail.com/

It was then discovered across multiple i5xxx drivers:

i5000_edac.c
i5100_edac.c
i5400_edac.c

This patch series aims to implement a fix for each of them.

             reply	other threads:[~2026-04-30  8:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30  8:42 Tushar Tibude [this message]
2026-04-30  8:42 ` [PATCH 1/3] EDAC: i5000: disable error reporting at teardown and refactor helper Tushar Tibude
2026-04-30  8:42 ` [PATCH 2/3] EDAC: i5100: disable error reporting at teardown and create helper Tushar Tibude
2026-04-30  8:42 ` [PATCH 3/3] EDAC: i5400: disable error reporting at teardown and refactor helper Tushar Tibude
2026-04-30 14:18 ` [PATCH 0/3] EDAC: fix error reporting handling during init for Zhuo, Qiuxu
2026-04-30 22:40   ` Luck, Tony
2026-05-01  2:07     ` Zhuo, Qiuxu

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=20260430084223.9298-1-tushar.tibude1000@gmail.com \
    --to=tushar.tibude1000@gmail.com \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=qiuxu.zhuo@intel.com \
    --cc=tony.luck@intel.com \
    /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