From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
Cc: Tom Rini <trini@konsulko.com>,
Jagan Teki <jagan@amarulasolutions.com>,
Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Vignesh R <vigneshr@ti.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
U-Boot-Denx <u-boot@lists.denx.de>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Steam Lin <stlin2@winbond.com>
Subject: Re: [PATCH] mtd: spinor: winbond: Describe several chips
Date: Wed, 19 Nov 2025 11:01:55 +0100 [thread overview]
Message-ID: <87cy5ecpd8.fsf@bootlin.com> (raw)
In-Reply-To: <CAOf5uwmygi5z3ae_wgJxu4LSKWfEHfAzPTWzN3TUCk22pHqikQ@mail.gmail.com> (Michael Nazzareno Trimarchi's message of "Wed, 19 Nov 2025 10:06:42 +0100")
Hi Michael,
On 19/11/2025 at 10:06:42 +01, Michael Nazzareno Trimarchi <michael@amarulasolutions.com> wrote:
> Hi Tom, and Miguel
>
> I pick a large part of the patches now, and check them and rebase all
> of them. I will prepare one pull request today and another later this
> week
What do you mean by "a large part"? Can you be more specific about
which patches you would not be picking and why?
I am not comfortable with this sentence given for how long these have
been reviewed and applied in Linux and also submitted to
U-Boot. Custodians are supposed to work in best effort mode, but
delaying, delaying and further delaying is not what I would qualify as
an adapted behaviour. I understand you have other work to do. I also
take my responsibility in reviewing and collecting and merging patches,
I may do errors and I correct them when that happens, but try not to put
all the pressure on my very own shoulders, down to the situation where
nothing moves anymore. Tom has been regularly trying to provide support
and help. I would friendly suggest Amarula folks to adopts a softer/more
progressive approach regarding maintainance roles.
Thanks,
Miquèl
next prev parent reply other threads:[~2025-11-19 15:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 17:02 [PATCH] mtd: spinor: winbond: Describe several chips Miquel Raynal
2025-09-09 10:12 ` Miquel Raynal
2025-11-13 9:50 ` Miquel Raynal
2025-11-13 14:27 ` Tom Rini
2025-11-13 14:36 ` Michael Nazzareno Trimarchi
2025-11-18 14:34 ` Tom Rini
2025-11-18 14:43 ` Michael Nazzareno Trimarchi
2025-11-19 9:06 ` Michael Nazzareno Trimarchi
2025-11-19 10:01 ` Miquel Raynal [this message]
2025-11-19 10:08 ` Michael Nazzareno Trimarchi
2025-11-19 20:55 ` Tom Rini
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=87cy5ecpd8.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=jagan@amarulasolutions.com \
--cc=michael@amarulasolutions.com \
--cc=stlin2@winbond.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=trini@konsulko.com \
--cc=tudor.ambarus@linaro.org \
--cc=u-boot@lists.denx.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