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

[Robert Jarzmik]

Boris Brezillon  writes:

>> Hi Boris,
>> 
>> So what's the status about the sync, should I pick the patches, and have the
>> others make it to your for-next branch ?
>
> It's been merged in l2-mtd/master (our -next branch) which is
> targeting 4.15. Unfortunately we didn't create a topic branch, which
> means you'll have to wait 4.15-rc1 before pushing patches 6 to 9 if you
> want avoid regressions. Anyway, I guess it's already too late to send
> PRs to arm-soc for 4.15.

Right, my next pull request is targetting v4.16.

Andrea, would you be so kind as to resend the serie (patches 6 - 9) on the
mailing list and to me, so that I review and apply the correct version.

Thanks.

-- 
Robert

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

[Robert Jarzmik]

Boris Brezillon  writes:

>> Hi Boris,
>> 
>> So what's the status about the sync, should I pick the patches, and have the
>> others make it to your for-next branch ?
>
> It's been merged in l2-mtd/master (our -next branch) which is
> targeting 4.15. Unfortunately we didn't create a topic branch, which
> means you'll have to wait 4.15-rc1 before pushing patches 6 to 9 if you
> want avoid regressions. Anyway, I guess it's already too late to send
> PRs to arm-soc for 4.15.

Right, my next pull request is targetting v4.16.

Andrea, would you be so kind as to resend the serie (patches 6 - 9) on the
mailing list and to me, so that I review and apply the correct version.

Thanks.

-- 
Robert

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

[Boris Brezillon]

On Sun, 08 Oct 2017 11:53:11 +0200
Robert Jarzmik  wrote:

> Robert Jarzmik  writes:
> 
> > Boris Brezillon  writes:
> >  
> >> Hi Robert,
> >> 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.  
> >
> > Hi Boris,
> >
> > It's targeting 4.15 right now. And we can do as you like, either an 
> > immutable
> > branch, or I wait to include these patches into my pxa/for-next until you 
> > give
> > me your go, it's as you like.  
> 
> Hi Boris,
> 
> So what's the status about the sync, should I pick the patches, and have the
> others make it to your for-next branch ?

It's been merged in l2-mtd/master (our -next branch) which is
targeting 4.15. Unfortunately we didn't create a topic branch, which
means you'll have to wait 4.15-rc1 before pushing patches 6 to 9 if you
want avoid regressions. Anyway, I guess it's already too late to send
PRs to arm-soc for 4.15.

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

[Boris Brezillon]

On Sun, 08 Oct 2017 11:53:11 +0200
Robert Jarzmik  wrote:

> Robert Jarzmik  writes:
> 
> > Boris Brezillon  writes:
> >  
> >> Hi Robert,
> >> 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.  
> >
> > Hi Boris,
> >
> > It's targeting 4.15 right now. And we can do as you like, either an 
> > immutable
> > branch, or I wait to include these patches into my pxa/for-next until you 
> > give
> > me your go, it's as you like.  
> 
> Hi Boris,
> 
> So what's the status about the sync, should I pick the patches, and have the
> others make it to your for-next branch ?

It's been merged in l2-mtd/master (our -next branch) which is
targeting 4.15. Unfortunately we didn't create a topic branch, which
means you'll have to wait 4.15-rc1 before pushing patches 6 to 9 if you
want avoid regressions. Anyway, I guess it's already too late to send
PRs to arm-soc for 4.15.

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

[Boris Brezillon]

On Sun, 8 Oct 2017 12:09:50 +0200
Boris Brezillon  wrote:

> On Sun, 08 Oct 2017 11:53:11 +0200
> Robert Jarzmik  wrote:
> 
> > Robert Jarzmik  writes:
> >   
> > > Boris Brezillon  writes:
> > >
> > >> Hi Robert,
> > >> 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.
> > >
> > > Hi Boris,
> > >
> > > It's targeting 4.15 right now. And we can do as you like, either an 
> > > immutable
> > > branch, or I wait to include these patches into my pxa/for-next until you 
> > > give
> > > me your go, it's as you like.
> > 
> > Hi Boris,
> > 
> > So what's the status about the sync, should I pick the patches, and have the
> > others make it to your for-next branch ?  
> 
> I'm still waiting Brian's final word about this version, and if he's
> happy with it, Richard will queue it for 4.15.

Actually, I'm waiting a feedback on v9 [1], not v5.

[1]http://patchwork.ozlabs.org/patch/808431/

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

[Boris Brezillon]

On Sun, 8 Oct 2017 12:09:50 +0200
Boris Brezillon  wrote:

> On Sun, 08 Oct 2017 11:53:11 +0200
> Robert Jarzmik  wrote:
> 
> > Robert Jarzmik  writes:
> >   
> > > Boris Brezillon  writes:
> > >
> > >> Hi Robert,
> > >> 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.
> > >
> > > Hi Boris,
> > >
> > > It's targeting 4.15 right now. And we can do as you like, either an 
> > > immutable
> > > branch, or I wait to include these patches into my pxa/for-next until you 
> > > give
> > > me your go, it's as you like.
> > 
> > Hi Boris,
> > 
> > So what's the status about the sync, should I pick the patches, and have the
> > others make it to your for-next branch ?  
> 
> I'm still waiting Brian's final word about this version, and if he's
> happy with it, Richard will queue it for 4.15.

Actually, I'm waiting a feedback on v9 [1], not v5.

[1]http://patchwork.ozlabs.org/patch/808431/

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

[Boris Brezillon]

On Sun, 08 Oct 2017 11:53:11 +0200
Robert Jarzmik  wrote:

> Robert Jarzmik  writes:
> 
> > Boris Brezillon  writes:
> >  
> >> Hi Robert,
> >> 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.  
> >
> > Hi Boris,
> >
> > It's targeting 4.15 right now. And we can do as you like, either an 
> > immutable
> > branch, or I wait to include these patches into my pxa/for-next until you 
> > give
> > me your go, it's as you like.  
> 
> Hi Boris,
> 
> So what's the status about the sync, should I pick the patches, and have the
> others make it to your for-next branch ?

I'm still waiting Brian's final word about this version, and if he's
happy with it, Richard will queue it for 4.15.

> 
> Cheers.
> 

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

[Boris Brezillon]

On Sun, 08 Oct 2017 11:53:11 +0200
Robert Jarzmik  wrote:

> Robert Jarzmik  writes:
> 
> > Boris Brezillon  writes:
> >  
> >> Hi Robert,
> >> 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.  
> >
> > Hi Boris,
> >
> > It's targeting 4.15 right now. And we can do as you like, either an 
> > immutable
> > branch, or I wait to include these patches into my pxa/for-next until you 
> > give
> > me your go, it's as you like.  
> 
> Hi Boris,
> 
> So what's the status about the sync, should I pick the patches, and have the
> others make it to your for-next branch ?

I'm still waiting Brian's final word about this version, and if he's
happy with it, Richard will queue it for 4.15.

> 
> Cheers.
> 

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

[Robert Jarzmik]

Robert Jarzmik  writes:

> Boris Brezillon  writes:
>
>> Hi Robert,
>> 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.
>
> Hi Boris,
>
> It's targeting 4.15 right now. And we can do as you like, either an immutable
> branch, or I wait to include these patches into my pxa/for-next until you give
> me your go, it's as you like.

Hi Boris,

So what's the status about the sync, should I pick the patches, and have the
others make it to your for-next branch ?

Cheers.

-- 
Robert

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

[Robert Jarzmik]

Robert Jarzmik  writes:

> Boris Brezillon  writes:
>
>> Hi Robert,
>> 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.
>
> Hi Boris,
>
> It's targeting 4.15 right now. And we can do as you like, either an immutable
> branch, or I wait to include these patches into my pxa/for-next until you give
> me your go, it's as you like.

Hi Boris,

So what's the status about the sync, should I pick the patches, and have the
others make it to your for-next branch ?

Cheers.

-- 
Robert

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

[Robert Jarzmik]

Boris Brezillon  writes:

> Hi Robert,
> 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.

Hi Boris,

It's targeting 4.15 right now. And we can do as you like, either an immutable
branch, or I wait to include these patches into my pxa/for-next until you give
me your go, it's as you like.

Cheers.

-- 
Robert

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

[Robert Jarzmik]

Boris Brezillon  writes:

> Hi Robert,
> 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.

Hi Boris,

It's targeting 4.15 right now. And we can do as you like, either an immutable
branch, or I wait to include these patches into my pxa/for-next until you give
me your go, it's as you like.

Cheers.

-- 
Robert

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

[Boris Brezillon]

Hi Robert,

On Thu, 24 Aug 2017 11:33:02 +0200
Andrea Adami  wrote:

> On Wed, Aug 23, 2017 at 9:33 PM, Robert Jarzmik  
> wrote:
> > Boris Brezillon  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

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

[Boris Brezillon]

Hi Robert,

On Thu, 24 Aug 2017 11:33:02 +0200
Andrea Adami  wrote:

> On Wed, Aug 23, 2017 at 9:33 PM, Robert Jarzmik  
> wrote:
> > Boris Brezillon  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

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

[Andrea Adami]

On Wed, Aug 23, 2017 at 9:33 PM, Robert Jarzmik  wrote:
> Boris Brezillon  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.
>
> Cheers.
>
> --
> Robert

Robert,

your suggestion is fine for me.
Please use " ARM: pxa: MACHINE: use sharpslpart parser instead of hardcoded one"

Thanks!
Andrea

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

[Andrea Adami]

On Wed, Aug 23, 2017 at 9:33 PM, Robert Jarzmik  wrote:
> Boris Brezillon  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.
>
> Cheers.
>
> --
> Robert

Robert,

your suggestion is fine for me.
Please use " ARM: pxa: MACHINE: use sharpslpart parser instead of hardcoded one"

Thanks!
Andrea

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

[Robert Jarzmik]

Boris Brezillon  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.

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.

Cheers.

-- 
Robert

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

[Robert Jarzmik]

Boris Brezillon  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.

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.

Cheers.

-- 
Robert

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

[Boris Brezillon]

Le Mon, 14 Aug 2017 22:48:31 +0200,
Andrea Adami  a écrit :

> This patchset introduces a simple partition parser for the Sharp SL
> Series PXA handhelds. More details in the commit text.
> 
> I have set in cc the ARM PXA maintainers because this is the MTD part of
> a planned wider patchset cleaning the Zaurus board files. The MFD maintainers
> are also in cc (tmio.h change).
> 
> Changelog:
> v1 firt version, initial import of 2.4 sources
> v2 refactor applying many suggested fixes
> v3 put the partition parser types in the platform data
> v4 refactor after ML review
> v5 fix commit messages and subject texts, remove global, fixes after v4 review
> 
> GPL sources: http://support.ezaurus.com/developer/source/source_dl.asp
> 
> 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.

Thanks,

Boris

>   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
> 
>  arch/arm/mach-pxa/corgi.c |  31 +---
>  arch/arm/mach-pxa/poodle.c|  28 +--
>  arch/arm/mach-pxa/spitz.c |  34 +---
>  arch/arm/mach-pxa/tosa.c  |  28 +--
>  drivers/mtd/nand/sharpsl.c|   2 +-
>  drivers/mtd/nand/tmio_nand.c  |   4 +-
>  drivers/mtd/parsers/Kconfig   |   8 +
>  drivers/mtd/parsers/Makefile  |   1 +
>  drivers/mtd/parsers/sharpslpart.c | 376 
> ++
>  include/linux/mfd/tmio.h  |   1 +
>  include/linux/mtd/sharpsl.h   |   1 +
>  11 files changed, 424 insertions(+), 90 deletions(-)
>  create mode 100644 drivers/mtd/parsers/sharpslpart.c
> 

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

[Boris Brezillon]

Le Mon, 14 Aug 2017 22:48:31 +0200,
Andrea Adami  a écrit :

> This patchset introduces a simple partition parser for the Sharp SL
> Series PXA handhelds. More details in the commit text.
> 
> I have set in cc the ARM PXA maintainers because this is the MTD part of
> a planned wider patchset cleaning the Zaurus board files. The MFD maintainers
> are also in cc (tmio.h change).
> 
> Changelog:
> v1 firt version, initial import of 2.4 sources
> v2 refactor applying many suggested fixes
> v3 put the partition parser types in the platform data
> v4 refactor after ML review
> v5 fix commit messages and subject texts, remove global, fixes after v4 review
> 
> GPL sources: http://support.ezaurus.com/developer/source/source_dl.asp
> 
> 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.

Thanks,

Boris

>   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
> 
>  arch/arm/mach-pxa/corgi.c |  31 +---
>  arch/arm/mach-pxa/poodle.c|  28 +--
>  arch/arm/mach-pxa/spitz.c |  34 +---
>  arch/arm/mach-pxa/tosa.c  |  28 +--
>  drivers/mtd/nand/sharpsl.c|   2 +-
>  drivers/mtd/nand/tmio_nand.c  |   4 +-
>  drivers/mtd/parsers/Kconfig   |   8 +
>  drivers/mtd/parsers/Makefile  |   1 +
>  drivers/mtd/parsers/sharpslpart.c | 376 
> ++
>  include/linux/mfd/tmio.h  |   1 +
>  include/linux/mtd/sharpsl.h   |   1 +
>  11 files changed, 424 insertions(+), 90 deletions(-)
>  create mode 100644 drivers/mtd/parsers/sharpslpart.c
>