2012/8/17 Artem Bityutskiy :
> Richard, would you please split this series differently:
>
> 1. Separate out the calculations to the get_bad_peb_limit() func.
> 2. Invent
> 2. Add the module parameter
> 3. Extends the ioctl
> 4. Removes the Kconfig option
>
> This will be much easier to review.
ok,
Richard, would you please split this series differently:
1. Separate out the calculations to the get_bad_peb_limit() func.
2. Invent
2. Add the module parameter
3. Extends the ioctl
4. Removes the Kconfig option
This will be much easier to review.
See also some comments below.
> ---
Richard, would you please split this series differently:
1. Separate out the calculations to the get_bad_peb_limit() func.
2. Invent
2. Add the module parameter
3. Extends the ioctl
4. Removes the Kconfig option
This will be much easier to review.
See also some comments below.
---
2012/8/17 Artem Bityutskiy dedeki...@gmail.com:
Richard, would you please split this series differently:
1. Separate out the calculations to the get_bad_peb_limit() func.
2. Invent
2. Add the module parameter
3. Extends the ioctl
4. Removes the Kconfig option
This will be much easier to
This patch provides the possibility to adjust the "maximum expected number of
bad blocks per 1024 blocks" (max_beb_per1024) for each mtd device.
The majority of NAND devices have their max_beb_per1024 equal to 20, but
sometimes it's more.
Now, we can adjust that via a kernel parameter:
This patch provides the possibility to adjust the maximum expected number of
bad blocks per 1024 blocks (max_beb_per1024) for each mtd device.
The majority of NAND devices have their max_beb_per1024 equal to 20, but
sometimes it's more.
Now, we can adjust that via a kernel parameter:
6 matches
Mail list logo