Hi Stefano, On Mon, Oct 24, 2016 at 7:51 PM, Jagan Teki <ja...@openedev.com> wrote: > On Mon, Oct 24, 2016 at 7:31 PM, Stefano Babic <sba...@denx.de> wrote: >> On 24/10/2016 15:15, Jagan Teki wrote: >>> On Mon, Oct 24, 2016 at 6:04 PM, Stefano Babic <sba...@denx.de> wrote: >>>> Hi Jagan, >> >>>> >>>> Please wait, I am confused. You have sent a complete V8, but as far as I >>>> understand the oinly changes are reported above (Patch 14/15). >>>> >>>> However, even if I have not tested, this would break bisecting, because >>>> patch 4/23 introduces the board and building with that commit leads to >>>> the error. So changes should be respective in patch 4 for mmc and patch >>>> 21 for NAND taking as reference V8. >>> >>> Yes, I've added 14/23 and 15/23 for new changes so the previous 14/21 >>> becomes 16/23 now and the only missing one is 21/23. So I will update >>> this 21/23 for v9. Hope this make clear for you. >> >> It is ok if you feel better to send V9 - what I meant it is just that >> entries for CONFIG_DM_MM and CONFIG_DM_MMC_OPS should be done in the >> same patch where the defconfig is added to avoid breaking bisecting. > > OK, then I will send the 14/23 with squash of 14/23 and 15/23 to 16/23 > and 21/23 v9. > Does it fine?
Sent these two patches with v9, please let me know for any issues. thanks! -- Jagan Teki Free Software Engineer | www.openedev.com U-Boot, Linux | Upstream Maintainer Hyderabad, India. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot