Hi York, My v8 version patch could you give me some advice? Some sata patch need rely on it to upstream, so if no other issue, could you help me merge it to upstream code
Thanks Best Regards, Yinbo Zhu -----Original Message----- From: Yinbo Zhu Sent: 2018年8月23日 11:10 To: York Sun <york....@nxp.com>; Y.b. Lu <yangbo...@nxp.com>; u-boot@lists.denx.de Cc: Xiaobo Xie <xiaobo....@nxp.com>; Andy Tang <andy.t...@nxp.com>; Peng Ma <peng...@nxp.com> Subject: RE: [PATCH v6 1/8] dm: mmc: use block layer in mmc driver -----Original Message----- From: York Sun Sent: 2018年8月15日 22:58 To: Yinbo Zhu <yinbo....@nxp.com>; Y.b. Lu <yangbo...@nxp.com>; u-boot@lists.denx.de Cc: Xiaobo Xie <xiaobo....@nxp.com>; Andy Tang <andy.t...@nxp.com>; Peng Ma <peng...@nxp.com> Subject: Re: [PATCH v6 1/8] dm: mmc: use block layer in mmc driver First of all, your subject is wrong. You are not making any change to dm or mmc. On 08/13/2018 12:09 AM, Yinbo Zhu wrote: > At present the MMC subsystem maintains its own list of MMC devices. > This cannot work with driver model when CONFIG_BLK is enabled, use > blk_dread to replace previous mmc read interface, use mmc_get_blk_desc > to get the mmc device property > > Signed-off-by: Yinbo Zhu <yinbo....@nxp.com> > --- > Change in v6: > remove block layer in mmc_legacy. > > arch/arm/cpu/armv8/fsl-layerscape/ppa.c | 5 ++--- >You didn't replace all. If you compiled all targets, you would see >errors on secure boot targets. Please fix >and test _ALL_ targets before sending another version. >York >Hi York, >I had tested all targets, for 1088 sd secure boot, upstream code has a >original issue, need upstream to >cover it other targets that I had tested okay, I will send it to upstream as >v7 version. >Thanks, >Best Regards, >Yinbo Zhu. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
