Linux CXL
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: linux-cxl@vger.kernel.org
Cc: djbw@kernel.org, dave@stgolabs.net, jic23@kernel.org,
	alison.schofield@intel.com, vishal.l.verma@intel.com
Subject: Re: [PATCH 0/3] cxl: Misc sashiko fixes
Date: Fri, 24 Jul 2026 07:58:22 -0700	[thread overview]
Message-ID: <61395775-5603-4582-a540-0d2aa60dec94@intel.com> (raw)
In-Reply-To: <20260722205303.3184787-1-dave.jiang@intel.com>



On 7/22/26 1:52 PM, Dave Jiang wrote:
> Several shashiko reported issues
> 1. cxl/memdev: Don't mask an earlier partition's poison query error
> 2. cxl/ras: Clear software-only TLP log fields after RCH AER copy
> 3. cxl/region: Guard against unset partition in poison_by_decoder()
> 
> 
> Dave Jiang (3):
>   cxl/region: Guard against unset partition in poison_by_decoder()
>   cxl/ras: Clear software-only TLP log fields after RCH AER copy
>   cxl/memdev: Don't mask an earlier partition's poison query error
> 
>  drivers/cxl/core/memdev.c  | 2 ++
>  drivers/cxl/core/ras_rch.c | 7 +++++++
>  drivers/cxl/core/region.c  | 3 +++
>  3 files changed, 12 insertions(+)
> 
> 
> base-commit: 1590cf0329716306e948a8fc29f1d3ee87d3989f


Ok ignore this series for now. I'm working it out with Alison and Terry to get them more organized into specific area series.

      parent reply	other threads:[~2026-07-24 14:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 20:52 [PATCH 0/3] cxl: Misc sashiko fixes Dave Jiang
2026-07-22 20:53 ` [PATCH 1/3] cxl/region: Guard against unset partition in poison_by_decoder() Dave Jiang
2026-07-22 21:10   ` sashiko-bot
2026-07-22 22:29     ` Dave Jiang
2026-07-22 20:53 ` [PATCH 2/3] cxl/ras: Clear software-only TLP log fields after RCH AER copy Dave Jiang
2026-07-22 21:10   ` sashiko-bot
2026-07-22 20:53 ` [PATCH 3/3] cxl/memdev: Don't mask an earlier partition's poison query error Dave Jiang
2026-07-22 21:04   ` sashiko-bot
2026-07-24 14:58 ` Dave Jiang [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=61395775-5603-4582-a540-0d2aa60dec94@intel.com \
    --to=dave.jiang@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=dave@stgolabs.net \
    --cc=djbw@kernel.org \
    --cc=jic23@kernel.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=vishal.l.verma@intel.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