From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Michael Walle" <mwalle@kernel.org>
Cc: "Itai Handler" <itai.handler@gmail.com>, <pratyush@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-mtd@lists.infradead.org>,
<vigneshr@ti.com>, <richard@nod.at>,
<takahiro.kuwano@infineon.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] mtd: spi-nor: fix the lock left held by spi_nor_rww_start_exclusive()
Date: Mon, 14 Sep 2026 14:34:32 +0200 [thread overview]
Message-ID: <874ifsovtz.fsf@bootlin.com> (raw)
In-Reply-To: <DLF191CC4QMM.1SNYEHUFJ9GK2@kernel.org> (Michael Walle's message of "Mon, 14 Sep 2026 14:20:05 +0200")
On 14/09/2026 at 14:20:05 +02, "Michael Walle" <mwalle@kernel.org> wrote:
>> Michael, since we already got a cycle with AI walls of text just to tell
>> "fix that damn conversion", can I (or you) apply that other patch, so we
>> can get rid of these? Let me know what you prefer, although I don't
>> remember where that thread is.
>
> It's already in spi-nor/next since last friday.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git/log/?h=spi-nor/next
> https://lore.kernel.org/linux-mtd/178913311701.1915651.4791624215787396187.b4-ty@b4/T/#me3b51a242469a4d9722089e18547e87fdc65d7c9
>
> -michael
Since that one is "big" I would have merged it through a fixes PR. I
usually send one around -rc4. So either you push the patch to mtd/fixes
(or I do it) and drop it from the spi-nor/next branch, or we keep things
like this, which is also kind of ok.
Regarding the use of `git push -f`, I know Richard, Pratyush & Tudor
highly dislike it and avoid to use it. I find this tool pretty useful on
branches like ours and prefer to drop a patch rather than carrying its
revert, or messing around with merges. I prefer a clean history rather
than the absolute lack of -f. We already have the (Linus) master branch
milestone which is set in stone, I don't get the need to create one
ourselves.
So, up to you ;)
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2026-09-14 12:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 8:11 [PATCH v2 0/3] mtd: spi-nor: fix the unlocked restore on shutdown and remove Itai Handler
2026-09-14 8:11 ` [PATCH v2 1/3] mtd: spi-nor: fix the lock left held by spi_nor_rww_start_exclusive() Itai Handler
2026-09-14 8:22 ` sashiko-bot
2026-09-14 12:09 ` Miquel Raynal
2026-09-14 12:20 ` Michael Walle
2026-09-14 12:34 ` Miquel Raynal [this message]
2026-09-14 12:41 ` Michael Walle
2026-09-14 13:11 ` Miquel Raynal
2026-09-14 8:11 ` [PATCH v2 2/3] mtd: spi-nor: take the flash lock in spi_nor_shutdown() Itai Handler
2026-09-14 8:24 ` sashiko-bot
2026-09-14 12:15 ` Miquel Raynal
2026-09-14 8:11 ` [PATCH v2 3/3] mtd: spi-nor: take the flash lock in spi_nor_remove() Itai Handler
2026-09-14 8:26 ` sashiko-bot
2026-09-14 12:19 ` Miquel Raynal
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=874ifsovtz.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=itai.handler@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mwalle@kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=stable@vger.kernel.org \
--cc=takahiro.kuwano@infineon.com \
--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.