Re: [PATCH v5 0/9] mtd: sharpslpart partition parser

Boris Brezillon
2017-08-24T09:46:31Z

Hi Robert,

On Thu, 24 Aug 2017 11:33:02 +0200
Andrea Adami <andrea.adami@gmail.com> wrote:

> On Wed, Aug 23, 2017 at 9:33 PM, Robert Jarzmik <robert.jarzmik@free.fr> wrote:
> > Boris Brezillon <boris.brezillon@free-electrons.com> writes:
> >
> >> Le Mon, 14 Aug 2017 22:48:31 +0200,
> >>> Andrea Adami (9):
> >>> mtd: sharpslpart: Add sharpslpart partition parser
> >>> mtd: nand: sharpsl: Add partition parsers platform data
> >>> mfd: tmio: Add partition parsers platform data
> >>> mtd: nand: sharpsl: Register partitions using the parsers
> >>> mtd: nand: tmio: Register partitions using the parsers
> >>
> >> Applied patches 2, to 5 to nand/next.
> >>> ARM: pxa/corgi: Remove hardcoded partitioning, use sharpslpart parser
> >>> ARM: pxa/tosa: Remove hardcoded partitioning, use sharpslpart parser
> >>> ARM: pxa/spitz: Remove hardcoded partitioning, use sharpslpart parser
> >>> ARM: pxa/poodle: Remove hardcoded partitioning, use sharpslpart parser
> >
> > I'm quite happy with patches 6 to 9 except for the subject title length.
> >
>
> Argh, this time I got it totally wrong with the titles of the patches!
> Sorry for the eye-sore.
>
> > Andrea, if you give me an idea of change, I'll modify the titles myself before
> > applying, no need to resend a serie.
> >
> > For example, you could propose :
> > ARM: pxa: corgi: use sharpslpart parser instead of hardcoded one
> >
> >
> > Then I'll take them into pxa/for-next if there are no objections.

Wait a bit before applying. I think patches 6 to 9 have a dependency on
patch 1 (it's not a build dependency, but NAND partitioning might be
wrong if you apply them), so we need to sync. What release is
pxa/for-next targeting? If it's 4.15 I can apply patch 1 just after
4.14-rc1 is out and provide an immutable branch for you to pull in
pxa/for-next.

Regards,

Boris