From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Stephen Horvath <s.horvath@outlook.com.au>,
Jean Delvare <jdelvare@suse.com>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Kamil Aronowski <kamil.aronowski@3mdeb.com>
Subject: Re: [PATCH v2 0/6] decode-dimms: Implement DDR5 decoding
Date: Wed, 14 Jan 2026 12:55:51 +0100 [thread overview]
Message-ID: <aWeERzS_BqFM4FLp@ninjato> (raw)
In-Reply-To: <20251106021356.208986-1-s.horvath@outlook.com.au>
On Thu, Nov 06, 2025 at 02:14:57AM +0000, Stephen Horvath wrote:
> Hi, this series of patches adds DDR5 support to decode-dimms.
>
> I'm not too experienced with perl or the JEDEC specs, so there's
> probably going to be some questionable choices here, but I'd love to
> hear feedback.
Jean, do you have time for this?
next prev parent reply other threads:[~2026-01-14 11:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 2:14 [PATCH v2 0/6] decode-dimms: Implement DDR5 decoding Stephen Horvath
2025-11-06 2:14 ` [PATCH v2 1/6] decode-dimms: Implement DDR5 checksum parsing Stephen Horvath
2025-11-06 2:14 ` [PATCH v2 2/6] decode-dimms: Decode DDR5 Manufacturer Data Stephen Horvath
2025-11-06 2:15 ` [PATCH v2 4/6] decode-dimms: Decode DDR5 common module information Stephen Horvath
2025-11-06 2:15 ` [PATCH v2 3/6] decode-dimms: Decode timings and other data for DDR5 Stephen Horvath
2025-11-06 2:15 ` [PATCH v2 5/6] decode-dimms: Add basic decoding of type specific information " Stephen Horvath
2025-11-06 2:15 ` [PATCH v2 6/6] decode-dimms: Decode DDR5 error log Stephen Horvath
2026-01-14 11:55 ` Wolfram Sang [this message]
2026-01-29 1:58 ` [PATCH v2 0/6] decode-dimms: Implement DDR5 decoding Darsey Litzenberger
2026-06-21 5:52 ` Stephen Horvath
2026-06-22 8:54 ` Wolfram Sang
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=aWeERzS_BqFM4FLp@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=jdelvare@suse.com \
--cc=kamil.aronowski@3mdeb.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=s.horvath@outlook.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.