From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Date: Wed, 24 Aug 2011 18:07:15 -0500 Subject: [U-Boot] [PATCH] README: clean up and document the Freescale QE/FMAN firmware macros In-Reply-To: <20110824225920.CE27511F9E78@gemini.denx.de> References: <1314049550-15993-1-git-send-email-timur@freescale.com> <20110824225920.CE27511F9E78@gemini.denx.de> Message-ID: <4E558423.8020803@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Wolfgang Denk wrote: > Dear Tabi Timur-B04825, > > In message you wrote: >> >>> Note that some of the code managed by these macros have not yet been posted > > s/have/has/ ? Thanks. >>> externally. Such code will be posted, but properly documenting the macros >>> is the first step. >> >> Wolfgang, if you're okay with the text in this patch, I will go ahead >> and make the corresponding changes to the code. I just want to make >> sure that there are no objections to these definitions before I work >> on the code itself. > > Sorry, but I don't even understand this. What does "post externally" > mean? Sorry, that's a term we use in Freescale. We have in-house code that has not yet been posted on this mailing list for the "official" U-Boot. That's what I mean by posting externally. I guess I need a better term for that. We also call that "upstream". > And why don't you add the documentation with the code? I haven't written the code yet. I want to make sure the idea is acceptable before I start implementing it. Plus, since our internal code is different than our "external" code, I need to manage both code bases independently. -- Timur Tabi Linux kernel developer at Freescale