public inbox for linux-edac@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: kyle-meyer <kyle.meyer@hpe.com>,
	dimitri.sivanich@hpe.com, steve.wahl@hpe.com, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	x86@kernel.org, hpa@zytor.com, tony.luck@intel.com,
	qiuxu.zhuo@intel.com, yazen.ghannam@amd.com,
	linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org
Subject: Re: [PATCH] RAS/CEC: Move non-debug attributes out of debugfs
Date: Thu, 23 Mar 2023 13:29:50 -0700	[thread overview]
Message-ID: <7d9679e9-6d1a-bb08-dbcc-acb833bd5fd8@intel.com> (raw)
In-Reply-To: <20230323202158.37937-1-kyle.meyer@hpe.com>

On 3/23/23 13:22, kyle-meyer wrote:
> From: Kyle Meyer <kyle.meyer@hpe.com>
> 
> When kernel lockdown is in effect, use of debugfs is not permitted. Move
> decay_interval and action_threshold out of debugfs, from debugfs/ras/cec
> to sysfs/system/devices/machinecheck/cec.

You forgot to attach the patch that you wrote that updates
Documentation/ABI/. ;)

Also, why *should* these be part of the stable sysfs ABI?  What app is
using them?  Why does it need them?  Why these two and only these two?
What's left in debugfs?

  reply	other threads:[~2023-03-23 20:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23 20:22 [PATCH] RAS/CEC: Move non-debug attributes out of debugfs kyle-meyer
2023-03-23 20:29 ` Dave Hansen [this message]
2023-03-23 21:52   ` Meyer, Kyle
2023-03-23 22:01     ` Dave Hansen
2023-03-24  0:49 ` Borislav Petkov
2023-03-24 20:50   ` Yazen Ghannam
2023-03-27 22:07     ` Borislav Petkov

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=7d9679e9-6d1a-bb08-dbcc-acb833bd5fd8@intel.com \
    --to=dave.hansen@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=dimitri.sivanich@hpe.com \
    --cc=hpa@zytor.com \
    --cc=kyle.meyer@hpe.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=qiuxu.zhuo@intel.com \
    --cc=steve.wahl@hpe.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=yazen.ghannam@amd.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