From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jagan Teki Date: Tue, 17 Oct 2017 02:59:25 +0530 Subject: [U-Boot] [PATCH v4 1/2] arm64: sun50i-h5.dtsi : add h5 & a64 compatible to mmc[0-2] In-Reply-To: <20171010171837.72b65vrp6evn6c3h@AntonyAntony.local> References: <20170921152217.4011-1-antony@phenome.org> <20171010133546.98061-1-antony@phenome.org> <20171010171837.72b65vrp6evn6c3h@AntonyAntony.local> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tue, Oct 10, 2017 at 10:48 PM, Antony Antony wrote: > On Tue, Oct 10, 2017 at 07:21:57PM +0530, Jagan Teki wrote: >> On Tue, Oct 10, 2017 at 7:18 PM, Peter Robinson wrote: >> > Shouldn't we just be syncing changes to the DT from the kernel? >> > > I guess syncing could possibly solve the problem! Kernel DTSI got the > compiltables I need from the begining. > > The diff looks big to me. I am not sure yet, I understand all changes. > Anyone who would like to sync the two files? Or willing to help me? > > diff ~/u-boot/arch/arm/dts/sun50i-h5.dtsi > ~/linux/arch/arm64/boot/dts/allwinner/sun50i-h5.dtsi > >> And add last merge commit details on commit message. > > A good point. I am wondering what is the practice for this u-boot commit > message. I do not see commit IDs mentioned. A few commits seems to mention > kernel version in the commit message. Getting merge ID details can help to check what details got synced, not a big deal. thanks! -- Jagan Teki Free Software Engineer | www.openedev.com U-Boot, Linux | Upstream Maintainer Hyderabad, India.