From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
To: Oded Gabbay <ogabbay@kernel.org>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Jeffrey Hugo <quic_jhugo@quicinc.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Arnd Bergmann <arnd@arndb.de>, John Hubbard <jhubbard@nvidia.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Christoph Hellwig <hch@infradead.org>,
Christopher Friedt <chrisfriedt@gmail.com>,
Kevin Hilman <khilman@baylibre.com>,
Jason Gunthorpe <jgg@nvidia.com>, Jiho Chu <jiho.chu@samsung.com>,
Alex Deucher <alexander.deucher@amd.com>,
Yuji Ishikawa <yuji2.ishikawa@toshiba.co.jp>,
Maciej Kwapulinski <maciej.kwapulinski@linux.intel.com>,
Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: [PATCH v4 0/4] new subsystem for compute accelerator devices
Date: Tue, 22 Nov 2022 11:17:12 +0100 [thread overview]
Message-ID: <eedd6611-dc35-b189-7ff2-fb7235048cdd@linux.intel.com> (raw)
In-Reply-To: <20221119204435.97113-1-ogabbay@kernel.org>
Hi,
On 11/19/2022 9:44 PM, Oded Gabbay wrote:
> This is the fourth (and hopefully last) version of the patch-set to add the
> new subsystem for compute accelerators. I removed the RFC headline as
> I believe it is now ready for merging.
Looks good and works without issues.
I will rebase next version of Intel VPU patchest on top of this.
Acked-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Tested-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Regards,
Jacek
WARNING: multiple messages have this Message-ID (diff)
From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
To: Oded Gabbay <ogabbay@kernel.org>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Jeffrey Hugo <quic_jhugo@quicinc.com>,
Jason Gunthorpe <jgg@nvidia.com>, Arnd Bergmann <arnd@arndb.de>,
Jiho Chu <jiho.chu@samsung.com>,
John Hubbard <jhubbard@nvidia.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Christoph Hellwig <hch@infradead.org>,
Christopher Friedt <chrisfriedt@gmail.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Kevin Hilman <khilman@baylibre.com>,
Alex Deucher <alexander.deucher@amd.com>,
Yuji Ishikawa <yuji2.ishikawa@toshiba.co.jp>,
Maciej Kwapulinski <maciej.kwapulinski@linux.intel.com>,
Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: [PATCH v4 0/4] new subsystem for compute accelerator devices
Date: Tue, 22 Nov 2022 11:17:12 +0100 [thread overview]
Message-ID: <eedd6611-dc35-b189-7ff2-fb7235048cdd@linux.intel.com> (raw)
In-Reply-To: <20221119204435.97113-1-ogabbay@kernel.org>
Hi,
On 11/19/2022 9:44 PM, Oded Gabbay wrote:
> This is the fourth (and hopefully last) version of the patch-set to add the
> new subsystem for compute accelerators. I removed the RFC headline as
> I believe it is now ready for merging.
Looks good and works without issues.
I will rebase next version of Intel VPU patchest on top of this.
Acked-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Tested-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Regards,
Jacek
next prev parent reply other threads:[~2022-11-22 10:17 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 20:44 [PATCH v4 0/4] new subsystem for compute accelerator devices Oded Gabbay
2022-11-19 20:44 ` Oded Gabbay
2022-11-19 20:44 ` [PATCH v4 1/4] drivers/accel: define kconfig and register a new major Oded Gabbay
2022-11-19 20:44 ` Oded Gabbay
2022-11-19 20:44 ` [PATCH v4 2/4] accel: add dedicated minor for accelerator devices Oded Gabbay
2022-11-19 20:44 ` Oded Gabbay
2022-11-20 21:47 ` Jeffrey Hugo
2022-11-20 21:47 ` Jeffrey Hugo
2022-11-21 15:11 ` Oded Gabbay
2022-11-21 15:11 ` Oded Gabbay
2022-11-19 20:44 ` [PATCH v4 3/4] drm: initialize accel framework Oded Gabbay
2022-11-19 20:44 ` Oded Gabbay
2022-11-22 10:55 ` Melissa Wen
2022-11-22 10:55 ` Melissa Wen
2022-11-22 10:59 ` Oded Gabbay
2022-11-22 10:59 ` Oded Gabbay
2022-11-22 11:02 ` Oded Gabbay
2022-11-22 11:02 ` Oded Gabbay
2022-11-22 11:11 ` Melissa Wen
2022-11-22 11:11 ` Melissa Wen
2022-11-19 20:44 ` [PATCH v4 4/4] doc: add documentation for accel subsystem Oded Gabbay
2022-11-19 20:44 ` Oded Gabbay
2022-11-20 22:01 ` Jeffrey Hugo
2022-11-20 22:01 ` Jeffrey Hugo
2022-11-21 15:18 ` Oded Gabbay
2022-11-21 15:18 ` Oded Gabbay
2022-11-21 15:26 ` Jeffrey Hugo
2022-11-21 15:26 ` Jeffrey Hugo
2022-11-20 15:26 ` [PATCH v4 0/4] new subsystem for compute accelerator devices Greg Kroah-Hartman
2022-11-20 15:26 ` Greg Kroah-Hartman
2022-11-20 22:04 ` Jeffrey Hugo
2022-11-20 22:04 ` Jeffrey Hugo
2022-11-22 15:57 ` Jeffrey Hugo
2022-11-22 15:57 ` Jeffrey Hugo
2022-11-21 6:25 ` Dave Airlie
2022-11-21 6:25 ` Dave Airlie
2022-11-21 15:11 ` Oded Gabbay
2022-11-21 15:11 ` Oded Gabbay
2022-11-21 15:08 ` Thomas Zimmermann
2022-11-21 15:08 ` Thomas Zimmermann
2022-11-21 15:57 ` Alex Deucher
2022-11-21 15:57 ` Alex Deucher
2022-11-21 15:58 ` Alex Deucher
2022-11-21 15:58 ` Alex Deucher
2022-11-21 23:06 ` Sonal Santan
2022-11-21 23:06 ` Sonal Santan
2022-11-22 5:46 ` Dave Airlie
2022-11-22 5:46 ` Dave Airlie
2022-11-22 14:54 ` Daniel Vetter
2022-11-22 14:54 ` Daniel Vetter
2022-11-23 14:02 ` Sonal Santan
2022-11-23 14:02 ` Sonal Santan
2022-11-22 10:17 ` Jacek Lawrynowicz [this message]
2022-11-22 10:17 ` Jacek Lawrynowicz
2022-11-23 12:27 ` Maxime Ripard
2022-11-23 12:27 ` Maxime Ripard
2022-11-24 18:34 ` Daniel Stone
2022-11-24 18:34 ` Daniel Stone
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=eedd6611-dc35-b189-7ff2-fb7235048cdd@linux.intel.com \
--to=jacek.lawrynowicz@linux.intel.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=arnd@arndb.de \
--cc=chrisfriedt@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jagan@amarulasolutions.com \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=jiho.chu@samsung.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.kwapulinski@linux.intel.com \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=tzimmermann@suse.de \
--cc=yuji2.ishikawa@toshiba.co.jp \
/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.