From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: 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: Thu, 28 Sep 2023 09:10:24 +0200 [thread overview]
Message-ID: <ZRUm4DS3qvRfcPox@ninjato> (raw)
In-Reply-To: <20230922163903.3f49ea2a@xps-13>
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
> 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.
I checked pxa_defconfig history. Most commits in the last 7 years were
just removing outdated Kconfig symbols from all kind of subsystems. Like
what we want to do here. I think it is okay to keep it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: 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: Thu, 28 Sep 2023 09:10:24 +0200 [thread overview]
Message-ID: <ZRUm4DS3qvRfcPox@ninjato> (raw)
In-Reply-To: <20230922163903.3f49ea2a@xps-13>
[-- Attachment #1.1: Type: text/plain, Size: 385 bytes --]
> 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.
I checked pxa_defconfig history. Most commits in the last 7 years were
just removing outdated Kconfig symbols from all kind of subsystems. Like
what we want to do here. I think it is okay to keep it.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 144 bytes --]
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: 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: Thu, 28 Sep 2023 09:10:24 +0200 [thread overview]
Message-ID: <ZRUm4DS3qvRfcPox@ninjato> (raw)
In-Reply-To: <20230922163903.3f49ea2a@xps-13>
[-- Attachment #1.1: Type: text/plain, Size: 385 bytes --]
> 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.
I checked pxa_defconfig history. Most commits in the last 7 years were
just removing outdated Kconfig symbols from all kind of subsystems. Like
what we want to do here. I think it is okay to keep it.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-09-28 7:14 UTC|newest]
Thread overview: 42+ 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 ` Wolfram Sang
2023-09-22 6:15 ` 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 6:15 ` Wolfram Sang
2023-09-22 6:15 ` Wolfram Sang
2023-09-22 14:39 ` Miquel Raynal
2023-09-22 14:39 ` Miquel Raynal
2023-09-22 14:39 ` Miquel Raynal
2023-09-22 17:55 ` Wolfram Sang
2023-09-22 17:55 ` Wolfram Sang
2023-09-22 17:55 ` Wolfram Sang
2023-09-22 18:35 ` Philippe Mathieu-Daudé
2023-09-22 18:35 ` Philippe Mathieu-Daudé
2023-09-22 18:35 ` Philippe Mathieu-Daudé
2023-09-25 7:11 ` Miquel Raynal
2023-09-25 7:11 ` Miquel Raynal
2023-09-25 7:11 ` Miquel Raynal
2023-09-28 7:10 ` Wolfram Sang [this message]
2023-09-28 7:10 ` Wolfram Sang
2023-09-28 7:10 ` Wolfram Sang
2023-10-02 9:39 ` Miquel Raynal
2023-10-02 9:39 ` Miquel Raynal
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
2023-10-19 8:50 ` Thomas Bogendoerfer
2023-10-19 8:50 ` 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=ZRUm4DS3qvRfcPox@ninjato \
--to=wsa+renesas@sang-engineering.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=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--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.