From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4 V2] doc: kerneldoc: Implant DocBook from Linux kernel
Date: Sun, 7 Oct 2012 01:06:00 +0200 [thread overview]
Message-ID: <201210070106.00426.marex@denx.de> (raw)
In-Reply-To: <20121004120722.0a8609a3@lilith>
Dear Albert ARIBAUD,
> Hi Marek,
>
> Comments based on the assumption that we want to sync with the Linux
> tools.
>
> General comment/hypothetical question: would it not be simpler to patch
> the existing Linux tools in-place so that we can use them on the U-Boot
> tree?
>
> Detailed comments below in this spirit; ignore if suggestion above is
> stupid/complicated/plain wrong/other(specify...or not).
[...]
Albert, can we just merge this version and resync when I get the patches into
upstream Linux? This is blocking the LG-arrays and other patches dependent on
them (like serial stuff).
The other option is to allow /** style comment. Wolfgang, can we do that?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-10-06 23:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-29 1:33 [U-Boot] [PATCH 0/4] Implant kernel-doc from Linux kernel Marek Vasut
2012-09-29 1:33 ` [U-Boot] [PATCH 1/4] doc: kerneldoc: Implant DocBook " Marek Vasut
2012-09-29 2:43 ` [U-Boot] [PATCH 1/4 V2] " Marek Vasut
2012-10-04 10:07 ` Albert ARIBAUD
2012-10-05 0:28 ` Marek Vasut
2012-10-05 0:35 ` Graeme Russ
2012-10-05 0:45 ` Marek Vasut
2012-10-05 18:55 ` Albert ARIBAUD
2012-10-06 23:06 ` Marek Vasut [this message]
2012-09-29 1:33 ` [U-Boot] [PATCH 2/4] doc: kerneldoc: Add nicer CSS stylesheet for HTML docs Marek Vasut
2012-09-29 1:33 ` [U-Boot] [PATCH 3/4] doc: kerneldoc: Implement "Example" section handling Marek Vasut
2012-09-29 1:33 ` [U-Boot] [PATCH 4/4] doc: kerneldoc: tmpl: Implement template for LG-arrays Marek Vasut
2012-09-30 0:21 ` [U-Boot] [PATCH 0/4 V2] Implant kernel-doc from Linux kernel Marek Vasut
2012-09-30 0:21 ` [U-Boot] [PATCH 1/4] doc: kerneldoc: Implant DocBook " Marek Vasut
2012-09-30 0:21 ` [U-Boot] [PATCH 2/4] doc: kerneldoc: Add nicer CSS stylesheet for HTML docs Marek Vasut
2012-09-30 0:21 ` [U-Boot] [PATCH 3/4] doc: kerneldoc: Implement "Example" section handling Marek Vasut
2012-09-30 0:21 ` [U-Boot] [PATCH 4/4] doc: kerneldoc: tmpl: Implement template for LG-arrays Marek Vasut
2012-10-02 18:28 ` [U-Boot] [PATCH 0/4 V2] Implant kernel-doc from Linux kernel Tom Rini
2012-10-06 23:26 ` Marek Vasut
2012-10-08 15:38 ` Tom Rini
2012-10-08 15:54 ` Marek Vasut
2012-10-09 22:35 ` Tom Rini
2012-10-09 22:37 ` Marek Vasut
2012-10-09 22:51 ` Tom Rini
2012-10-07 0:04 ` [U-Boot] [PATCH 1/4 V3] kerneldoc: Implant DocBook " Marek Vasut
2012-10-07 0:04 ` [U-Boot] [PATCH 2/4 V3] kerneldoc: Add nicer CSS stylesheet for HTML docs Marek Vasut
2012-10-07 0:05 ` [U-Boot] [PATCH 3/4 V3] kerneldoc: Implement "Example" section handling Marek Vasut
2012-10-07 0:05 ` [U-Boot] [PATCH 4/4 V3] kerneldoc: Add myself to the git-mailrc for kerneldoc Marek Vasut
2012-10-22 21:29 ` [U-Boot] [PATCH 1/4 V3] kerneldoc: Implant DocBook from Linux kernel Andy Fleming
2012-10-23 7:30 ` Marek Vasut
2012-10-23 19:56 ` Andy Fleming
2012-10-23 20:58 ` Tom Rini
2012-10-23 21:03 ` Andy Fleming
2012-10-25 18:50 ` Tom Rini
2012-10-25 19:04 ` Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201210070106.00426.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox