mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fenghua Yu <fenghua.yu@intel.com>
To: Vinod Koul <vkoul@kernel.org>, Dave Jiang <dave.jiang@intel.com>
Cc: <dmaengine@vger.kernel.org>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] Expose IAA 2.0 device capabilities
Date: Tue, 28 Mar 2023 19:01:46 -0700	[thread overview]
Message-ID: <9f233d86-d8a6-f28d-93e5-e2614d7e9f9b@intel.com> (raw)
In-Reply-To: <20230303213732.3357494-1-fenghua.yu@intel.com>

Hi, Vinod,

On 3/3/23 13:37, Fenghua Yu wrote:
> In-memory Analytics Accelerator (IAA) 2.0 [1] introduces General
> Capabilities Register (GENCAP). Add a sysfs attribute to expose the
> register to applications.
> 
> This series is applied cleanly on top of DSA 2.0 Event Log and Completion
> Record Faulting series:
> https://lore.kernel.org/dmaengine/20230103163505.1569356-1-fenghua.yu@intel.com/T/#m13ba6167994f3add6446d2d7e242ecb637c54426

Correction: this series does not depend on DSA 2.0 Event Log and 
Completion Record Faulting series. This series itself can be applied 
cleanly on top of upstream kernel.

Any comment on this series? Will you pick it up?

Thank you very much!

-Fenghua

  parent reply	other threads:[~2023-03-29  2:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 21:37 Fenghua Yu
2023-03-03 21:37 ` [PATCH v2 1/2] dmaengine: idxd: reformat swerror output to standard Linux bitmap output Fenghua Yu
2023-03-03 21:37 ` [PATCH v2 2/2] dmaengine: idxd: expose IAA CAP register via sysfs knob Fenghua Yu
2023-03-29  2:01 ` Fenghua Yu [this message]
2023-03-31 11:57 ` [PATCH v2 0/2] Expose IAA 2.0 device capabilities Vinod Koul
2023-03-31 15:57   ` Fenghua Yu

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=9f233d86-d8a6-f28d-93e5-e2614d7e9f9b@intel.com \
    --to=fenghua.yu@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vkoul@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
all inboxes | Powered by JetHome®