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 v4 01/11] mtd: core: always create master device
Date: Wed, 15 Jan 2025 20:22:25 +0100 [thread overview]
Message-ID: <871px3lw5q.fsf@bootlin.com> (raw)
In-Reply-To: <CY5PR11MB63663795A6C4DC83CB89602AED182@CY5PR11MB6366.namprd11.prod.outlook.com> (Alexander Usyskin's message of "Tue, 14 Jan 2025 14:05:40 +0000")
Hi,
On 14/01/2025 at 14:05:40 GMT, "Usyskin, Alexander" <alexander.usyskin@intel.com> wrote:
>> > > Create master device without partition when
>> > > CONFIG_MTD_PARTITIONED_MASTER flag is unset.
>> >
>> > I don't think you took into consideration my remarks regarding the fact
>> > that you would break userspace. If you enable the master, you no longer
>> > have the same device numbering in userspace. I know people should not
>> > care about these numbers, but in practice they do.
>> >
>> > If I'm wrong, please be a little more verbose about why :)
>> >
>> > Thanks,
>> > Miquèl
>>
>> Hi Miquel
>>
>> I've created separate class (mtd_master) for such devices.
>> Uses-space looking for mtd device continues to receive same number of
>> /dev/mtdX devices.
>> There will be additional /dev/mtd_masterX devices, but this is unavoidable, I
>> suppose.
>> Maybe we can rename it to something that not in /dev/mtd* expression (e.g.
>> mastermtdX),
>> if it helps.
>>
>
> Miquel, is this good enough or requires rewrite?
This is an important change that requires attention, and at the time I
have not been able to dedicate enough to this patch.
Also, if the other mtd maintainers want to help, I'll be enthousiastic
about it :)
Thanks,
Miquèl
WARNING: multiple messages have this Message-ID (diff)
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 v4 01/11] mtd: core: always create master device
Date: Wed, 15 Jan 2025 20:22:25 +0100 [thread overview]
Message-ID: <871px3lw5q.fsf@bootlin.com> (raw)
In-Reply-To: <CY5PR11MB63663795A6C4DC83CB89602AED182@CY5PR11MB6366.namprd11.prod.outlook.com> (Alexander Usyskin's message of "Tue, 14 Jan 2025 14:05:40 +0000")
Hi,
On 14/01/2025 at 14:05:40 GMT, "Usyskin, Alexander" <alexander.usyskin@intel.com> wrote:
>> > > Create master device without partition when
>> > > CONFIG_MTD_PARTITIONED_MASTER flag is unset.
>> >
>> > I don't think you took into consideration my remarks regarding the fact
>> > that you would break userspace. If you enable the master, you no longer
>> > have the same device numbering in userspace. I know people should not
>> > care about these numbers, but in practice they do.
>> >
>> > If I'm wrong, please be a little more verbose about why :)
>> >
>> > Thanks,
>> > Miquèl
>>
>> Hi Miquel
>>
>> I've created separate class (mtd_master) for such devices.
>> Uses-space looking for mtd device continues to receive same number of
>> /dev/mtdX devices.
>> There will be additional /dev/mtd_masterX devices, but this is unavoidable, I
>> suppose.
>> Maybe we can rename it to something that not in /dev/mtd* expression (e.g.
>> mastermtdX),
>> if it helps.
>>
>
> Miquel, is this good enough or requires rewrite?
This is an important change that requires attention, and at the time I
have not been able to dedicate enough to this patch.
Also, if the other mtd maintainers want to help, I'll be enthousiastic
about it :)
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2025-01-15 19:22 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 15:39 [PATCH v4 00/11] mtd: add driver for Intel discrete graphics Alexander Usyskin
2025-01-01 15:39 ` Alexander Usyskin
2025-01-01 15:39 ` [PATCH v4 01/11] mtd: core: always create master device Alexander Usyskin
2025-01-01 15:39 ` Alexander Usyskin
2025-01-06 10:46 ` Miquel Raynal
2025-01-06 10:46 ` Miquel Raynal
2025-01-06 11:03 ` Usyskin, Alexander
2025-01-06 11:03 ` Usyskin, Alexander
2025-01-14 14:05 ` Usyskin, Alexander
2025-01-14 14:05 ` Usyskin, Alexander
2025-01-15 19:22 ` Miquel Raynal [this message]
2025-01-15 19:22 ` Miquel Raynal
2025-01-15 22:30 ` Richard Weinberger
2025-01-15 22:30 ` Richard Weinberger
2025-01-16 6:54 ` Usyskin, Alexander
2025-01-16 6:54 ` Usyskin, Alexander
2025-01-17 22:27 ` Richard Weinberger
2025-01-17 22:27 ` Richard Weinberger
2025-01-19 7:30 ` Usyskin, Alexander
2025-01-19 7:30 ` Usyskin, Alexander
2025-01-01 15:39 ` [PATCH v4 02/11] mtd: add driver for intel graphics non-volatile memory device Alexander Usyskin
2025-01-01 15:39 ` Alexander Usyskin
2025-01-02 10:32 ` Christophe JAILLET
2025-01-02 10:32 ` Christophe JAILLET
2025-01-02 13:20 ` Usyskin, Alexander
2025-01-02 13:20 ` Usyskin, Alexander
2025-01-01 15:39 ` [PATCH v4 03/11] mtd: intel-dg: implement region enumeration Alexander Usyskin
2025-01-01 15:39 ` Alexander Usyskin
2025-01-02 10:37 ` Christophe JAILLET
2025-01-02 10:37 ` Christophe JAILLET
2025-01-02 10:49 ` Usyskin, Alexander
2025-01-02 10:49 ` Usyskin, Alexander
2025-01-01 15:39 ` [PATCH v4 04/11] mtd: intel-dg: implement access functions Alexander Usyskin
2025-01-01 15:39 ` Alexander Usyskin
2025-01-01 15:39 ` [PATCH v4 05/11] mtd: intel-dg: register with mtd Alexander Usyskin
2025-01-01 15:39 ` Alexander Usyskin
2025-01-01 15:39 ` [PATCH v4 06/11] mtd: intel-dg: align 64bit read and write Alexander Usyskin
2025-01-01 15:39 ` Alexander Usyskin
2025-01-01 16:41 ` David Laight
2025-01-01 16:41 ` David Laight
2025-01-01 21:16 ` David Laight
2025-01-01 21:16 ` David Laight
2025-01-02 13:56 ` Usyskin, Alexander
2025-01-02 13:56 ` Usyskin, Alexander
2025-01-01 15:39 ` [PATCH v4 07/11] mtd: intel-dg: wake card on operations Alexander Usyskin
2025-01-01 15:39 ` Alexander Usyskin
2025-01-29 21:51 ` Rodrigo Vivi
2025-01-29 21:51 ` Rodrigo Vivi
2025-02-11 5:32 ` Poosa, Karthik
2025-02-11 5:32 ` Poosa, Karthik
2025-02-12 14:15 ` Usyskin, Alexander
2025-02-12 14:15 ` Usyskin, Alexander
2025-01-01 15:39 ` [PATCH v4 08/11] drm/i915/nvm: add nvm device for discrete graphics Alexander Usyskin
2025-01-01 15:39 ` Alexander Usyskin
2025-01-01 15:39 ` [PATCH v4 09/11] drm/i915/nvm: add support for access mode Alexander Usyskin
2025-01-01 15:39 ` Alexander Usyskin
2025-01-01 15:39 ` [PATCH v4 10/11] drm/xe/nvm: add on-die non-volatile memory device Alexander Usyskin
2025-01-01 15:39 ` Alexander Usyskin
2025-01-29 21:36 ` Rodrigo Vivi
2025-01-29 21:36 ` Rodrigo Vivi
2025-01-01 15:39 ` [PATCH v4 11/11] drm/xe/nvm: add support for access mode Alexander Usyskin
2025-01-01 15:39 ` Alexander Usyskin
2025-01-01 16:17 ` ✗ Fi.CI.CHECKPATCH: warning for mtd: add driver for Intel discrete graphics (rev4) Patchwork
2025-01-01 16:17 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-01-01 16:33 ` ✗ i915.CI.BAT: failure " Patchwork
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=871px3lw5q.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 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.