Hi Boris,
On Wed, Jan 6, 2016 at 10:29 PM, Boris Brezillon
wrote:
> On Wed, 30 Dec 2015 09:31:06 +0100
> Boris Brezillon wrote:
>
>> Hi Peter,
>>
>> On Wed, 30 Dec 2015 15:18:39 +0800
>> 潘栋 wrote:
>>
>> > Hi Boris and Ezequiel,
>> >
>> > 2015-12-29 23:11 GMT+08:00 Boris Brezillon
>> > :
>> >
On Wed, 30 Dec 2015 09:31:06 +0100
Boris Brezillon wrote:
> Hi Peter,
>
> On Wed, 30 Dec 2015 15:18:39 +0800
> 潘栋 wrote:
>
> > Hi Boris and Ezequiel,
> >
> > 2015-12-29 23:11 GMT+08:00 Boris Brezillon
> > :
> > > On Tue, 29 Dec 2015 12:07:50 -0300
> > > Ezequiel Garcia wrote:
> > >
> > >>
On Wed, 30 Dec 2015 09:31:06 +0100
Boris Brezillon wrote:
> Hi Peter,
>
> On Wed, 30 Dec 2015 15:18:39 +0800
> 潘栋 wrote:
>
> > Hi Boris and Ezequiel,
> >
> > 2015-12-29 23:11 GMT+08:00 Boris Brezillon
> >
Hi Boris,
On Wed, Jan 6, 2016 at 10:29 PM, Boris Brezillon
wrote:
> On Wed, 30 Dec 2015 09:31:06 +0100
> Boris Brezillon wrote:
>
>> Hi Peter,
>>
>> On Wed, 30 Dec 2015 15:18:39 +0800
>> 潘栋 wrote:
Hi Peter,
On Wed, 30 Dec 2015 15:18:39 +0800
潘栋 wrote:
> Hi Boris and Ezequiel,
>
> 2015-12-29 23:11 GMT+08:00 Boris Brezillon
> :
> > On Tue, 29 Dec 2015 12:07:50 -0300
> > Ezequiel Garcia wrote:
> >
> >> On 29 December 2015 at 06:35, Boris Brezillon
> >> wrote:
> >> > Hi,
> >> >
> >> > On
Hi Peter,
On Wed, 30 Dec 2015 15:18:39 +0800
潘栋 wrote:
> Hi Boris and Ezequiel,
>
> 2015-12-29 23:11 GMT+08:00 Boris Brezillon
> :
> > On Tue, 29 Dec 2015 12:07:50 -0300
> > Ezequiel Garcia wrote:
> >
Hi Boris and Ezequiel,
2015-12-29 23:11 GMT+08:00 Boris Brezillon :
> On Tue, 29 Dec 2015 12:07:50 -0300
> Ezequiel Garcia wrote:
>
>> On 29 December 2015 at 06:35, Boris Brezillon
>> wrote:
>> > Hi,
>> >
>> > On Mon, 28 Dec 2015 17:42:50 -0300
>> > Ezequiel Garcia wrote:
>> >
>> >> This is
On Tue, 29 Dec 2015 12:07:50 -0300
Ezequiel Garcia wrote:
> On 29 December 2015 at 06:35, Boris Brezillon
> wrote:
> > Hi,
> >
> > On Mon, 28 Dec 2015 17:42:50 -0300
> > Ezequiel Garcia wrote:
> >
> >> This is looking a lot better, thanks for the good work!
> >>
> >> On 15 December 2015 at
On 29 December 2015 at 06:35, Boris Brezillon
wrote:
> Hi,
>
> On Mon, 28 Dec 2015 17:42:50 -0300
> Ezequiel Garcia wrote:
>
>> This is looking a lot better, thanks for the good work!
>>
>> On 15 December 2015 at 02:59, Peter Pan wrote:
>> > Currently nand_bbt.c is tied with struct nand_chip,
Hi,
On Mon, 28 Dec 2015 17:42:50 -0300
Ezequiel Garcia wrote:
> This is looking a lot better, thanks for the good work!
>
> On 15 December 2015 at 02:59, Peter Pan wrote:
> > Currently nand_bbt.c is tied with struct nand_chip, and it makes other
> > NAND family chips hard to use nand_bbt.c.
Hi Boris and Ezequiel,
2015-12-29 23:11 GMT+08:00 Boris Brezillon :
> On Tue, 29 Dec 2015 12:07:50 -0300
> Ezequiel Garcia wrote:
>
>> On 29 December 2015 at 06:35, Boris Brezillon
>> wrote:
Hi,
On Mon, 28 Dec 2015 17:42:50 -0300
Ezequiel Garcia wrote:
> This is looking a lot better, thanks for the good work!
>
> On 15 December 2015 at 02:59, Peter Pan wrote:
> > Currently nand_bbt.c is tied with struct nand_chip, and it
On 29 December 2015 at 06:35, Boris Brezillon
wrote:
> Hi,
>
> On Mon, 28 Dec 2015 17:42:50 -0300
> Ezequiel Garcia wrote:
>
>> This is looking a lot better, thanks for the good work!
>>
>> On 15 December 2015 at 02:59, Peter Pan
On Tue, 29 Dec 2015 12:07:50 -0300
Ezequiel Garcia wrote:
> On 29 December 2015 at 06:35, Boris Brezillon
> wrote:
> > Hi,
> >
> > On Mon, 28 Dec 2015 17:42:50 -0300
> > Ezequiel Garcia wrote:
> >
This is looking a lot better, thanks for the good work!
On 15 December 2015 at 02:59, Peter Pan wrote:
> 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
This is looking a lot better, thanks for the good work!
On 15 December 2015 at 02:59, Peter Pan wrote:
> 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
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 can make current BBT shareable.
We create struct nand_bbt to take place of
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 can make current BBT shareable.
We create struct nand_bbt to take place of
18 matches
Mail list logo