Linux I2C development
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Stephen Horvath <s.horvath@outlook.com.au>
Cc: "dlitz@dlitz.net" <dlitz@dlitz.net>,
	Jean Delvare <jdelvare@suse.de>,
	"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: Mon, 22 Jun 2026 10:54:58 +0200	[thread overview]
Message-ID: <ajj4YuedtNBEElVv@ninjato> (raw)
In-Reply-To: <SYBPR01MB4586E27116CAFBB44B16C493C5E02@SYBPR01MB4586.ausprd01.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 252 bytes --]

Hi Stephen,

> Here's a quick patch I just threw together, I'll probably also submit a v3
> eventually.

Please do. I already have plans for a 4.5 release of the tools and this
would be a great addition to have!

Thanks and happy hacking,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-06-22  8: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 3/6] decode-dimms: Decode timings and other data for DDR5 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 5/6] decode-dimms: Add basic decoding of type specific information for DDR5 Stephen Horvath
2025-11-06  2:15 ` [PATCH v2 6/6] decode-dimms: Decode DDR5 error log Stephen Horvath
2026-01-14 11:55 ` [PATCH v2 0/6] decode-dimms: Implement DDR5 decoding Wolfram Sang
2026-01-29  1:58 ` Darsey Litzenberger
2026-06-21  5:52   ` Stephen Horvath
2026-06-22  8:54     ` Wolfram Sang [this message]

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=ajj4YuedtNBEElVv@ninjato \
    --to=wsa+renesas@sang-engineering.com \
    --cc=dlitz@dlitz.net \
    --cc=jdelvare@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox