Hi Peter,
On Mon, 28 Mar 2016 16:20:19 +0800
Peter Pan wrote:
> Hi Ezequiel,
>
> Sorry for reply your mail late. And thaks a lot for reviewing it.
>
> On Thu, Mar 24, 2016 at 4:57 AM, Ezequiel Garcia
> wrote:
> > Hello,
> >
> > On 13 March 2016 at 23:47, Peter Pan wrote:
> >> Sorry for send
Hi Ezequiel,
Sorry for reply your mail late. And thaks a lot for reviewing it.
On Thu, Mar 24, 2016 at 4:57 AM, Ezequiel Garcia
wrote:
> Hello,
>
> On 13 March 2016 at 23:47, Peter Pan wrote:
>> Sorry for send the v3 out late. I went through a busy time in the past
>> two month.
>>
>> Currently
On Fri, Mar 25, 2016 at 4:50 PM, Boris Brezillon
wrote:
> On Mon, 14 Mar 2016 02:47:53 +
> Peter Pan wrote:
>
>> Sorry for send the v3 out late. I went through a busy time in the past
>> two month.
>>
>> Currently nand_bbt.c is tied with struct nand_chip, and it makes other
>> NAND family chi
On Mon, 14 Mar 2016 02:47:53 +
Peter Pan wrote:
> Sorry for send the v3 out late. I went through a busy time in the past
> two month.
>
> Currently nand_bbt.c is tied with struct nand_chip, and it makes other
> NAND family chips hard to use nand_bbt.c. Maybe it's the reason why
> onenand has
Hello,
On 13 March 2016 at 23:47, Peter Pan wrote:
> Sorry for send the v3 out late. I went through a busy time in the past
> two month.
>
> Currently nand_bbt.c is tied with struct nand_chip, and it makes other
> NAND family chips hard to use nand_bbt.c. Maybe it's the reason why
> onenand has o
Hi Peter,
On Mon, 14 Mar 2016 10:57:49 +0800
Peter Pan wrote:
> Sorry I forgot to add subject prefix. Should I re-send it ?
No that should be fine. Thanks for reworking this series as suggested.
I'll try to review it soon.
>
> On Mon, Mar 14, 2016 at 10:47 AM, Peter Pan wrote:
> > Sorry for
Sorry I forgot to add subject prefix. Should I re-send it ?
On Mon, Mar 14, 2016 at 10:47 AM, Peter Pan wrote:
> Sorry for send the v3 out late. I went through a busy time in the past
> two month.
>
> Currently nand_bbt.c is tied with struct nand_chip, and it makes other
> NAND family chips hard
Sorry for send the v3 out late. I went through a busy time in the past
two month.
Currently nand_bbt.c is tied with struct nand_chip, and it makes other
NAND family chips hard to use nand_bbt.c. Maybe it's the reason why
onenand has own bbt(onenand_bbt.c).
Separate struct nand_chip from BBT code
8 matches
Mail list logo