From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-mips@vger.kernel.org, Jonas Gorski <jonas.gorski@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH v2 2/6] mtd: parsers: ar7: remove support
Date: Mon, 25 Sep 2023 09:11:25 +0200 [thread overview]
Message-ID: <20230925091125.299caa92@xps-13> (raw)
In-Reply-To: <52ba27b9-79d5-f9cc-450f-fe831e65769a@linaro.org>
Hi,
philmd@linaro.org wrote on Fri, 22 Sep 2023 20:35:16 +0200:
> On 22/9/23 19:55, Wolfram Sang wrote:
> >
> >> I'm not sure it is wise to merge defconfig changes through mtd. Would
> >> you mind sending this change aside to avoid potential conflicts? Each
> >> patch can live on their own anyway.
> >
> > Yup, I can send a seperate patch for it.
> >
> >>> drivers/mtd/parsers/Kconfig | 5 --
> >>> drivers/mtd/parsers/Makefile | 1 -
> >>> drivers/mtd/parsers/ar7part.c | 129 ---------------------------------
> >>
> >> Do you have other changes related to this file in your tree? It failed
> >> to apply on my side.
> >
> > No change. Plain v6.6-rc2. I used "--irreversible-delete", though. Maybe
> > this is causing issues? As I stated in the cover-letter, I wonder if all
> > this should go via MIPS. But there hasn't been any discussion about it
> > yet.
>
> MIPS tree for the whole series certainly makes sense.
Then:
Acked-by: Miquel Raynal <miquel.raynal@bootlin.com>
Thanks,
Miquèl
next prev parent reply other threads:[~2023-09-25 7:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 6:15 [PATCH v2 0/6] remove AR7 platform and associated drivers Wolfram Sang
2023-09-22 6:15 ` [PATCH v2 1/6] serial: 8250: remove AR7 support Wolfram Sang
2023-09-22 6:15 ` [PATCH v2 2/6] mtd: parsers: ar7: remove support Wolfram Sang
2023-09-22 14:39 ` Miquel Raynal
2023-09-22 17:55 ` Wolfram Sang
2023-09-22 18:35 ` Philippe Mathieu-Daudé
2023-09-25 7:11 ` Miquel Raynal [this message]
2023-09-28 7:10 ` Wolfram Sang
2023-10-02 9:39 ` Miquel Raynal
2023-09-22 6:15 ` [PATCH v2 3/6] vlynq: remove bus driver Wolfram Sang
2023-09-22 6:15 ` [PATCH v2 4/6] watchdog: ar7_wdt: remove driver to prepare for platform removal Wolfram Sang
2023-09-22 6:15 ` [PATCH net-next v2 5/6] net: cpmac: " Wolfram Sang
2023-10-05 14:08 ` Thomas Bogendoerfer
2023-10-05 14:16 ` Jakub Kicinski
2023-10-05 19:07 ` Thomas Bogendoerfer
2023-10-06 14:26 ` Jakub Kicinski
2023-09-22 6:15 ` [PATCH v2 6/6] MIPS: AR7: remove platform Wolfram Sang
2023-09-28 7:06 ` Wolfram Sang
2023-09-28 7:29 ` Thomas Bogendoerfer
2023-09-28 7:49 ` Wolfram Sang
2023-10-06 8:20 ` Thomas Bogendoerfer
2023-10-19 8:49 ` Thomas Bogendoerfer
2023-10-19 12:32 ` Wolfram Sang
2023-10-19 8:50 ` [PATCH v2 0/6] remove AR7 platform and associated drivers Thomas Bogendoerfer
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=20230925091125.299caa92@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=f.fainelli@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=philmd@linaro.org \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).