public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: fenghua.yu@intel.com, dave.jiang@intel.com,
	dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH V2 0/3] dmaengine: idxd: Error path fixes
Date: Wed, 28 Dec 2022 16:25:32 +0530	[thread overview]
Message-ID: <Y6wgpI7cbicyUgj8@matsya> (raw)
In-Reply-To: <cover.1670452419.git.reinette.chatre@intel.com>

On 07-12-22, 14:52, Reinette Chatre wrote:
> Changes since v1:
> - V1: https://lore.kernel.org/lkml/cover.1670005163.git.reinette.chatre@intel.com/
> - Cover trimmed after obtaining needed information.
> - Added Reviewed-by tags.
> - cc stable team.
> - Please see individual patches for patch specific changes.
> 
> Dear Maintainers,
> 
> I have been using the IDXD driver to experiment with the upcoming core
> changes in support of IMS ([1], [2], [3]). As part of this work I
> happened to exercise the error paths within IDXD and encountered
> a few issues that are addressed in this series. These changes are
> independent from IMS and just aims to make the IDXD driver more
> robust against errors.
> 
> Your feedback is greatly appreciated.

Applied, thanks

-- 
~Vinod

      parent reply	other threads:[~2022-12-28 10:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07 22:52 [PATCH V2 0/3] dmaengine: idxd: Error path fixes Reinette Chatre
2022-12-07 22:52 ` [PATCH V2 1/3] dmaengine: idxd: Let probe fail when workqueue cannot be enabled Reinette Chatre
2022-12-07 22:52 ` [PATCH V2 2/3] dmaengine: idxd: Prevent use after free on completion memory Reinette Chatre
2022-12-07 22:52 ` [PATCH V2 3/3] dmaengine: idxd: Do not call DMX TX callbacks during workqueue disable Reinette Chatre
2022-12-28 10:55 ` Vinod Koul [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=Y6wgpI7cbicyUgj8@matsya \
    --to=vkoul@kernel.org \
    --cc=dave.jiang@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=fenghua.yu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=stable@vger.kernel.org \
    /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