From: Mike Rapoport <rppt@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
Boris Brezillon <boris.brezillon@collabora.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: [PATCH v2 1/3] ARM: pxa: remove Compulab pxa2xx boards
Date: Thu, 21 May 2020 22:01:58 +0300 [thread overview]
Message-ID: <20200521190158.GL1118872@kernel.org> (raw)
In-Reply-To: <CAK8P3a2XdG_u6_o2NbQDTb5dbdzByBkUXZNM6nZ3wz0c-LFT5w@mail.gmail.com>
On Thu, May 21, 2020 at 09:26:10AM +0200, Arnd Bergmann wrote:
> On Thu, May 21, 2020 at 9:12 AM Mike Rapoport <rppt@kernel.org> wrote:
> >
> > On Wed, May 20, 2020 at 05:21:51PM +0200, Arnd Bergmann wrote:
> > > On Wed, May 20, 2020 at 12:21 PM Robert Jarzmik <robert.jarzmik@free.fr> wrote:
> > > >
> > > > As these boards have no more users nor testers, and patching them has
> > > > become a burden, be that because of the PCI part or the MTD NAND
> > > > support, let's remove them.
> > > >
> > > > The cm-x300 will for now remain and represent Compulab boards at its
> > > > best in the PXA department.
> >
> > I think this series missed the cm-x270 NAND driver, so this could be
> > PATCH 4/3 (not even compile tested).
> >
> > From 56a11987f82ef8b32b25dfc17b849f9bbbf03e4d Mon Sep 17 00:00:00 2001
> > From: Mike Rapoport <rppt@linux.ibm.com>
> > Date: Thu, 21 May 2020 10:09:47 +0300
> > Subject: [PATCH] mtd: rawnand: remove CM-X270 NAND driver
> >
> > The cm-x270 board have been removed and theres is no point to keep this
> > driver.
> >
> > Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
>
> Thanks! Removing that driver was actually how the discussion started,
> so we definitely want to do that. Boris earlier patch "mtd: rawnand: Get
> rid of the cmx270 driver" did it by changing the board file, now your
> patch is the right thing to do, and we should remember to do the same
> for mbxfb.
Arnd, will you pick this to the SoC tree or should I resend?
> Arnd
--
Sincerely yours,
Mike.
_______________________________________________
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:[~2020-05-21 19:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 10:21 [PATCH v2 1/3] ARM: pxa: remove Compulab pxa2xx boards Robert Jarzmik
2020-05-20 10:21 ` [PATCH v2 2/3] MAINTAINERS: pxa: remove Compulab arm/pxa support Robert Jarzmik
2020-05-20 10:21 ` [PATCH v2 3/3] ASoC: pxa: remove Compulab pxa2xx boards Robert Jarzmik
2020-05-20 13:58 ` Arnd Bergmann
2020-05-20 15:21 ` [PATCH v2 1/3] ARM: " Arnd Bergmann
2020-05-20 15:57 ` Mike Rapoport
2020-05-21 9:01 ` Robert Jarzmik
2020-05-21 7:12 ` Mike Rapoport
2020-05-21 7:26 ` Arnd Bergmann
2020-05-21 19:01 ` Mike Rapoport [this message]
2020-05-21 19:10 ` Boris Brezillon
2020-05-22 11:18 ` Miquel Raynal
2020-05-22 13:14 ` Arnd Bergmann
2020-05-22 13:17 ` Miquel Raynal
2020-05-22 13:22 ` Arnd Bergmann
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=20200521190158.GL1118872@kernel.org \
--to=rppt@kernel.org \
--cc=arnd@arndb.de \
--cc=boris.brezillon@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=robert.jarzmik@free.fr \
/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).