Hi Jaehoon,
On 21 July 2016 at 22:14, Jaehoon Chung wrote:
> Hi Simon,
>
> On 07/22/2016 12:21 PM, Simon Glass wrote:
>> Hi Kever,
>>
>> On 19 July 2016 at 07:28, Kever Yang wrote:
>>> Not like the mmc-legacy which the devnum starts from 1, it
Hi Simon,
On 07/22/2016 12:21 PM, Simon Glass wrote:
> Hi Kever,
>
> On 19 July 2016 at 07:28, Kever Yang wrote:
>> Not like the mmc-legacy which the devnum starts from 1, it starts from 0
>> in mmc-uclass, so the device number should be (devnum + 1) in get_mmc_num().
Hi Kever,
On 19 July 2016 at 07:28, Kever Yang wrote:
> Not like the mmc-legacy which the devnum starts from 1, it starts from 0
> in mmc-uclass, so the device number should be (devnum + 1) in get_mmc_num().
>
> Signed-off-by: Kever Yang
>
Hi Kever,
On 07/19/2016 10:28 PM, Kever Yang wrote:
> Not like the mmc-legacy which the devnum starts from 1, it starts from 0
> in mmc-uclass, so the device number should be (devnum + 1) in get_mmc_num().
Looks good to me. I had already sent the similar patch for this.
Not like the mmc-legacy which the devnum starts from 1, it starts from 0
in mmc-uclass, so the device number should be (devnum + 1) in get_mmc_num().
Signed-off-by: Kever Yang
---
Changes in v3:
- apply comments from Jaehoon Chung
Changes in v2:
- add comment for
5 matches
Mail list logo