From: Borislav Petkov <bp@alien8.de>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Tony Luck <tony.luck@intel.com>,
Yazen Ghannam <yazen.ghannam@amd.com>,
Muralidhara M K <muralimk@amd.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
Muralidhara M K <muralidhara.mk@amd.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: Begin a RAS section
Date: Tue, 9 Jan 2024 19:36:46 +0100 [thread overview]
Message-ID: <20240109183646.GAZZ2SPiMZv83J3f0a@fat_crate.local> (raw)
In-Reply-To: <87a5pes8jy.fsf@meer.lwn.net>
On Tue, Jan 09, 2024 at 10:47:29AM -0700, Jonathan Corbet wrote:
> I wish I'd been copied on this ...
linux-doc was CCed:
https://lore.kernel.org/all/20231128142049.GTZWX3QQTSaQk%2F+u53@fat_crate.local/
Or did you prefer you directly?
I've been working to get a handle on
> the top-level Documentation/ directories for a while, and would rather
> not see a new one added for this. Offhand, based on this first
> document, it looks like material that belongs under
> Documentation/admin-guide; can we move it there, please?
Not really an admin guide thing - yes, based on the current content but
actually, the aim for this is to document all things RAS, so it is more
likely a subsystem thing. And all the subsystems are directories under
Documentation/.
So where do you want me to put it?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2024-01-09 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231102114225.2006878-1-muralimk@amd.com>
[not found] ` <20231102114225.2006878-2-muralimk@amd.com>
2023-11-28 14:20 ` [PATCH] Documentation: Begin a RAS section Borislav Petkov
2023-11-28 15:23 ` Yazen Ghannam
2023-11-28 17:04 ` Randy Dunlap
2023-11-28 19:39 ` Borislav Petkov
2024-01-09 17:47 ` Jonathan Corbet
2024-01-09 18:36 ` Borislav Petkov [this message]
2024-01-09 19:44 ` Jonathan Corbet
2024-01-09 20:04 ` Borislav Petkov
2024-01-24 12:40 ` Borislav Petkov
2024-02-05 19:41 ` 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=20240109183646.GAZZ2SPiMZv83J3f0a@fat_crate.local \
--to=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muralidhara.mk@amd.com \
--cc=muralimk@amd.com \
--cc=tony.luck@intel.com \
--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