From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Mon, 8 Oct 2012 08:38:44 -0700 Subject: [U-Boot] [PATCH 0/4 V2] Implant kernel-doc from Linux kernel In-Reply-To: <201210070126.12138.marex@denx.de> References: <1348882394-20629-1-git-send-email-marex@denx.de> <1348964495-12606-1-git-send-email-marex@denx.de> <20121002182851.GE655@bill-the-cat> <201210070126.12138.marex@denx.de> Message-ID: <5072F384.9080700@ti.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/06/12 16:26, Marek Vasut wrote: > Dear Tom Rini, > >> On Sun, Sep 30, 2012 at 02:21:31AM +0200, Marek Vasut wrote: >>> This patch series implants slightly modified kernel-doc >>> documentation generator from Linux kernel into U-Boot. First >>> patch pulls in all the necessary components with minor >>> modifications made to them to work with the layout of U-Boot >>> source tree and without kbuild. >>> >>> Further patch implement CSS to make the HTML documentation >>> look a bit nicer. This patch will eventually (hopefully) be >>> further refined by someone more artistically capable than me >>> ;-) >>> >>> Next patch implements separate handling for "Example:" >>> section, which in the original kernel-doc was in my opinion >>> mistreated. The example section generated a block of code, but >>> the indentation was removed. Thus this patch does avoid >>> removing the indent. >>> >>> Finally, the last patch implements example of how to use this >>> kernel-doc to generate U-Boot documentation by documenting the >>> Linker-Generated arrays. >>> >>> NOTE: This patchset (last patch) has a cross-dependency on: >>> [PATCH 0/5] Linker-generated arrays (take 2) >>> >>> V2: Add proper .gitignore entries, fix build issues (fix >>> Makefiles) >> >> Thanks for doing all this. It looks fine and I'll grab this >> with the LG-arrays code once everyone is happy on that side. > > I'm spliting the LG-array dep from these ... but I have another > problem. If I actually add the patman tags here (which I did now), > can you pull that repo without pulling the tags too? How do we > handle that ? We talked about this on IRC, but to be clear and for the record: - - No pull requests from patman branches - - Just do a 'git checkout -b final/feature base_branch' or whatever and then just 'git am 0*' the patches that patman will have spit out for you already. - -- Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQcvOEAAoJENk4IS6UOR1WCeMQAIMQwHlea3YRYF7lqoXuQVI3 xyrDV+c502TWh+uHUMUHjzYo7StGmOhzC/0WOkjn9hCB2bT1uzHqYWOJ2e8Hl7gG eHiWLJrYIq6+s7sZh8lKORiQY4AVyqMzuYNz6xmdWAw8s1N9T3tEN9Mw1AfNXy/G tL6E+UXo47zHjVzunWa3opaiUVx7C4ofWrQ1zsqPnY+IaVUX4NdCeVJt6vQLNKOD iCXm5eCqD8J+eEGxLh9jgekZXC2pnb11GJeMB0tOZPkYrLU6o3kdNlqW6WGUgXJb cV0bwIvJJhqTH1j1asd1b8t5dfMK0qlVVmI/FzgWc0ADwJqlGXKUWng5EoERaYN1 dxM+E8NwP+78VLCtZJKH+g5RkczSm5ZuDkxgrAbIZAajclxrEUN+IZp5zv4iG7iF kWjNiGYWXAE+0GpVJEFH2iVi1sTmvJCYcFspsyP+SSJWEq71Xoe/4YXyEYYCg/Wa ffv557zo4lF+fh4DCjUBOrk1XzBOZP2cMHT272+gQ4bYLHFJqKypSaqS+en+hHAZ dheb6tLYbzavE8mNN4cX6LQeRgwfjArf5DaqRJqnwAkma2pfM7fLw6wqSUrVGPBf alM1dA59h2Tnv6pg7BiQSRGCvyyk29C3KZAJSNECCPCvrVO4X1/+kaASVGfZ81bY cGmT10suFww/Y4C2O1GF =7f2b -----END PGP SIGNATURE-----