Re: [PATCH] mtd: bcm47xxpart: fix parsing first block after aligned TRX

2016-11-22 Thread Brian Norris
On Sun, Nov 20, 2016 at 04:09:30PM +0100, Rafał Miłecki wrote: > From: Rafał Miłecki > > After parsing TRX we should skip to the first block placed behind it. > Our code was working only with TRX with length not aligned to the > blocksize. In other cases (length aligned) it was

Re: [PATCH] mtd: bcm47xxpart: fix parsing first block after aligned TRX

2016-11-22 Thread Brian Norris
On Sun, Nov 20, 2016 at 04:09:30PM +0100, Rafał Miłecki wrote: > From: Rafał Miłecki > > After parsing TRX we should skip to the first block placed behind it. > Our code was working only with TRX with length not aligned to the > blocksize. In other cases (length aligned) it was missing the block

[PATCH] mtd: bcm47xxpart: fix parsing first block after aligned TRX

2016-11-20 Thread Rafał Miłecki
From: Rafał Miłecki After parsing TRX we should skip to the first block placed behind it. Our code was working only with TRX with length not aligned to the blocksize. In other cases (length aligned) it was missing the block places right after TRX. This fixes calculation and

[PATCH] mtd: bcm47xxpart: fix parsing first block after aligned TRX

2016-11-20 Thread Rafał Miłecki
From: Rafał Miłecki After parsing TRX we should skip to the first block placed behind it. Our code was working only with TRX with length not aligned to the blocksize. In other cases (length aligned) it was missing the block places right after TRX. This fixes calculation and simplifies the