public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Richard Weinberger <richard@nod.at>,
	 Michael Walle <mwalle@kernel.org>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	 Tudor Ambarus <tudor.ambarus@linaro.org>,
	 pratyush <pratyush@kernel.org>,
	 linux-mtd <linux-mtd@lists.infradead.org>,
	 Alexander Usyskin <alexander.usyskin@intel.com>
Subject: Re: [PATCH] Revert "mtd: core: always create master device"
Date: Tue, 17 Jun 2025 15:35:04 +0200	[thread overview]
Message-ID: <87plf2mqyf.fsf@bootlin.com> (raw)
In-Reply-To: <deb4072f-f6b3-4d7c-b19b-109570183aa9@roeck-us.net> (Guenter Roeck's message of "Mon, 16 Jun 2025 09:49:55 -0700")

Hi,

On 16/06/2025 at 09:49:55 -07, Guenter Roeck <linux@roeck-us.net> wrote:

> On 6/16/25 01:21, Richard Weinberger wrote:
>> ----- Ursprüngliche Mail -----
>>> Von: "Michael Walle" <mwalle@kernel.org>
>>>> This reverts commit 0aa7b390fc40a871267a2328bbbefca8b37ad307.
>>>>
>>>> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
>>>
>>> Should this have a Fixes tag?
>> Since we're in the same release cycle no back-porting is needed.
>> 
>
> This applies to Stable: tags, but not to Fixes:. A patch fixing a
> previous patch from the same release cycle should still be tagged
> with Fixes:.

All right, I'll add the Fixes and send a v2.

In the mean time, any ack's to provide folks? I'd like to merge it this
week and avoid other bug reports.

Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2025-06-17 14:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 18:07 [PATCH] Revert "mtd: core: always create master device" Miquel Raynal
2025-06-16  8:17 ` Michael Walle
2025-06-16  8:21   ` Richard Weinberger
2025-06-16 16:49     ` Guenter Roeck
2025-06-17 13:35       ` Miquel Raynal [this message]
2025-06-17 13:55         ` Guenter Roeck
2025-06-17 13:53 ` Guenter Roeck

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=87plf2mqyf.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=alexander.usyskin@intel.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux@roeck-us.net \
    --cc=mwalle@kernel.org \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=tudor.ambarus@linaro.org \
    --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