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: Mon, 5 Feb 2024 20:41:12 +0100 [thread overview]
Message-ID: <20240205194112.GGZcE52DXtK2lr0-14@fat_crate.local> (raw)
In-Reply-To: <20240124124030.GDZbEFPo4APcggdE33@fat_crate.local>
On Wed, Jan 24, 2024 at 01:40:30PM +0100, Borislav Petkov wrote:
> From: "Borislav Petkov (AMD)" <bp@alien8.de>
> Date: Wed, 24 Jan 2024 13:37:52 +0100
> Subject: [PATCH] Documentation: Move RAS section to admin-guide
>
> This is where this stuff should be.
>
> Requested-by: Jonathan Corbet <corbet@lwn.net>
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
> ---
> Documentation/RAS/index.rst | 14 --------------
> .../{ => admin-guide}/RAS/address-translation.rst | 0
> .../{ => admin-guide}/RAS/error-decoding.rst | 0
> Documentation/admin-guide/RAS/index.rst | 7 +++++++
> .../admin-guide/{ras.rst => RAS/main.rst} | 10 +++++++---
> Documentation/admin-guide/index.rst | 2 +-
> Documentation/index.rst | 1 -
> 7 files changed, 15 insertions(+), 19 deletions(-)
> delete mode 100644 Documentation/RAS/index.rst
> rename Documentation/{ => admin-guide}/RAS/address-translation.rst (100%)
> rename Documentation/{ => admin-guide}/RAS/error-decoding.rst (100%)
> create mode 100644 Documentation/admin-guide/RAS/index.rst
> rename Documentation/admin-guide/{ras.rst => RAS/main.rst} (99%)
Now queued.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2024-02-05 19:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 11:42 [PATCH v3 0/4] Few cleanups and AMD Family 19h Models 90h-9fh EDAC Support Muralidhara M K
2023-11-02 11:42 ` [PATCH v3 1/4] EDAC/mce_amd: Remove SMCA Extended Error code descriptions Muralidhara M K
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
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 [this message]
2023-11-28 14:24 ` [tip: ras/core] EDAC/mce_amd: Remove SMCA Extended Error code descriptions tip-bot2 for Muralidhara M K
2023-11-02 11:42 ` [PATCH v3 2/4] x86/MCE/AMD: Add new MA_LLC, USR_DP, and USR_CP bank types Muralidhara M K
2023-11-29 10:33 ` [tip: ras/core] " tip-bot2 for Muralidhara M K
2023-11-02 11:42 ` [PATCH v3 3/4] EDAC/mc: Add support for HBM3 memory type Muralidhara M K
2023-11-02 11:42 ` [PATCH v3 4/4] EDAC/amd64: Add support for family 0x19, models 0x90-9f devices Muralidhara M K
2023-11-29 10:26 ` [PATCH v3 0/4] Few cleanups and AMD Family 19h Models 90h-9fh EDAC Support 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=20240205194112.GGZcE52DXtK2lr0-14@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;
as well as URLs for NNTP newsgroup(s).