From: Brian Norris <computersforpeace@gmail.com>
To: Boris BREZILLON <boris.brezillon@free-electrons.com>
Cc: linux-mtd@lists.infradead.org,
Randy Dunlap <rdunlap@infradead.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd: nand: fix DocBook warnings on nand_sdr_timings doc
Date: Tue, 19 Aug 2014 12:00:00 -0700 [thread overview]
Message-ID: <20140819190000.GU18411@ld-irv-0074> (raw)
In-Reply-To: <1408264182-31830-1-git-send-email-boris.brezillon@free-electrons.com>
On Sun, Aug 17, 2014 at 10:29:42AM +0200, Boris BREZILLON wrote:
> Change the comment type (from /** to /*) to prevent DocBook from
> complaining about missing description for nand_sdr_timings fields.
>
> There is currently no need in documenting those fields because they are
> fully described in the ONFI specification (which is pointed out in the
> comment).
>
> Signed-off-by: Boris BREZILLON <boris.brezillon@free-electrons.com>
Pushed to linux-mtd.git. Thanks!
Brian
prev parent reply other threads:[~2014-08-19 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-17 8:29 [PATCH] mtd: nand: fix DocBook warnings on nand_sdr_timings doc Boris BREZILLON
2014-08-17 16:30 ` Randy Dunlap
2014-08-19 19:00 ` Brian Norris [this message]
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=20140819190000.GU18411@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rdunlap@infradead.org \
/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