intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alexander Usyskin <alexander.usyskin@intel.com>
Cc: "Richard Weinberger" <richard@nod.at>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"Lucas De Marchi" <lucas.demarchi@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Jani Nikula" <jani.nikula@linux.intel.com>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Tvrtko Ursulin" <tursulin@ursulin.net>,
	"Oren Weil" <oren.jer.weil@intel.com>,
	linux-mtd@lists.infradead.org, dri-devel@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/10] mtd: add driver for Intel discrete graphics
Date: Mon, 11 Nov 2024 20:59:58 +0100	[thread overview]
Message-ID: <87y11po81t.fsf@bootlin.com> (raw)
In-Reply-To: <20241107131356.2796969-1-alexander.usyskin@intel.com> (Alexander Usyskin's message of "Thu, 7 Nov 2024 15:13:46 +0200")

Hello Alexander,

On 07/11/2024 at 15:13:46 +02, Alexander Usyskin <alexander.usyskin@intel.com> wrote:

> Add driver for access to Intel discrete graphics card
> internal NVM device.
> Expose device on auxiliary bus by i915 and Xe drivers and
> provide mtd driver to register this device with MTD framework.
>
> This is a rewrite of "drm/i915/spi: spi access for discrete graphics"
> and "spi: add driver for Intel discrete graphics"
> series with connection to the Xe driver and splitting
> the spi driver part to separate module in mtd subsystem.
>
> This series intended to be pushed through drm-xe-next.

Overall the mtd bits look fine, I don't want to block this series
further so you can add on the mtd patches my

Acked-by: Miquel Raynal <miquel.raynal@bootlin.com>

Thanks,
Miquèl

      parent reply	other threads:[~2024-11-11 20:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 13:13 [PATCH v2 00/10] mtd: add driver for Intel discrete graphics Alexander Usyskin
2024-11-07 13:13 ` [PATCH v2 01/10] mtd: add driver for intel graphics non-volatile memory device Alexander Usyskin
2024-11-07 13:13 ` [PATCH v2 02/10] mtd: intel-dg: implement region enumeration Alexander Usyskin
2024-11-07 13:13 ` [PATCH v2 03/10] mtd: intel-dg: implement access functions Alexander Usyskin
2024-11-07 13:13 ` [PATCH v2 04/10] mtd: intel-dg: register with mtd Alexander Usyskin
2024-11-07 13:13 ` [PATCH v2 05/10] mtd: intel-dg: align 64bit read and write Alexander Usyskin
2024-11-07 13:13 ` [PATCH v2 06/10] mtd: intel-dg: wake card on operations Alexander Usyskin
2024-11-07 13:13 ` [PATCH v2 07/10] drm/i915/nvm: add nvm device for discrete graphics Alexander Usyskin
2024-11-07 21:40   ` Rodrigo Vivi
2024-11-07 13:13 ` [PATCH v2 08/10] drm/i915/nvm: add support for access mode Alexander Usyskin
2024-11-07 21:41   ` Rodrigo Vivi
2024-11-07 13:13 ` [PATCH v2 09/10] drm/xe/nvm: add on-die non-volatile memory device Alexander Usyskin
2024-11-07 13:13 ` [PATCH v2 10/10] drm/xe/nvm: add support for access mode Alexander Usyskin
2024-11-07 21:38   ` Rodrigo Vivi
2024-11-07 13:55 ` ✗ Fi.CI.CHECKPATCH: warning for mtd: add driver for Intel discrete graphics (rev2) Patchwork
2024-11-07 13:55 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-07 14:15 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-11-11 19:59 ` Miquel Raynal [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=87y11po81t.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=airlied@gmail.com \
    --cc=alexander.usyskin@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lucas.demarchi@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=oren.jer.weil@intel.com \
    --cc=richard@nod.at \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tursulin@ursulin.net \
    --cc=tzimmermann@suse.de \
    --cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).