public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Usyskin, Alexander" <alexander.usyskin@intel.com>
Cc: "Richard Weinberger" <richard@nod.at>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"De Marchi, Lucas" <lucas.demarchi@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Vivi, Rodrigo" <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>,
	"Poosa, Karthik" <karthik.poosa@intel.com>,
	"Abliyev, Reuven" <reuven.abliyev@intel.com>,
	"Weil, Oren jer" <oren.jer.weil@intel.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7 01/12] mtd: core: always create master device
Date: Mon, 12 May 2025 10:25:31 +0200	[thread overview]
Message-ID: <87h61qnslg.fsf@bootlin.com> (raw)
In-Reply-To: <CY5PR11MB6366C40CC20B3519476DD8E2ED892@CY5PR11MB6366.namprd11.prod.outlook.com> (Alexander Usyskin's message of "Tue, 6 May 2025 11:07:21 +0000")

Hello Alexander,

On 06/05/2025 at 11:07:21 GMT, "Usyskin, Alexander" <alexander.usyskin@intel.com> wrote:

>> 
>> On 26/03/2025 at 17:26:12 +02, Alexander Usyskin
>> <alexander.usyskin@intel.com> wrote:
>> 
>> > Create master device without partition when
>> > CONFIG_MTD_PARTITIONED_MASTER flag is unset.
>> >
>> > This streamlines device tree and allows to anchor
>> > runtime power management on master device in all cases.
>> >
>> > Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
>> 
>> Applied to mtd/next. Thanks!
>> 
>> Miquèl
>
> Thanks a lot!
>
> Miquel, would you pick patches from this series for files that are
> in the mtd tree?
> I can send separate patch series for this.
> In this case the i915/Xe patches can be merged in parallel via Xe
> tree.

I read several times that these patches should go through drm somehow,
so I provided my Ack. I do not think build would be broken if patch 1
goes through mtd and the others through drm anyway, especially since drm
has some structural slowness which means once applied to drm-misc(-next)
they may be part of the main tree a release later (iiuc).

However, I might drop this patch and reapply the one from v9, because I
apparently messed up with the version count. There is no action required
on your side.

Thanks,
Miquèl

  reply	other threads:[~2025-05-12  8:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 15:26 [PATCH v7 00/12] mtd: add driver for Intel discrete graphics Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 01/12] mtd: core: always create master device Alexander Usyskin
2025-04-01 15:00   ` Miquel Raynal
2025-04-07 12:47     ` Usyskin, Alexander
2025-04-09  9:59       ` Miquel Raynal
2025-04-10  9:44         ` Usyskin, Alexander
2025-04-10 14:12           ` Usyskin, Alexander
2025-04-29  9:23   ` Miquel Raynal
2025-05-06 11:07     ` Usyskin, Alexander
2025-05-12  8:25       ` Miquel Raynal [this message]
2025-03-26 15:26 ` [PATCH v7 02/12] mtd: add driver for intel graphics non-volatile memory device Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 03/12] mtd: intel-dg: implement region enumeration Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 04/12] mtd: intel-dg: implement access functions Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 05/12] mtd: intel-dg: register with mtd Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 06/12] mtd: intel-dg: align 64bit read and write Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 07/12] mtd: intel-dg: wake card on operations Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 08/12] drm/i915/nvm: add nvm device for discrete graphics Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 09/12] drm/i915/nvm: add support for access mode Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 10/12] drm/xe/nvm: add on-die non-volatile memory device Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 11/12] drm/xe/nvm: add support for access mode Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 12/12] drm/xe/nvm: add support for non-posted erase Alexander Usyskin
2025-03-26 19:22 ` [PATCH v7 00/12] mtd: add driver for Intel discrete graphics Rodrigo Vivi
2025-04-09  9:33   ` Usyskin, Alexander

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=87h61qnslg.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=karthik.poosa@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=reuven.abliyev@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