public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Brian Norris" <computersforpeace@gmail.com>
To: "Artem Bityutskiy" <dedekind1@gmail.com>
Cc: brian.foster@maxim-ic.com,
	Brian Norris <computersforpeace@gmail.com>,
	linux-mtd@lists.infradead.org
Subject: [PATCH v2 7/9] faq: ubi(fs): sending bug reports using `mtdinfo'
Date: Tue, 9 Aug 2011 15:03:54 -0700	[thread overview]
Message-ID: <1312927434-16708-1-git-send-email-computersforpeace@gmail.com> (raw)
In-Reply-To: <1312832239-21759-8-git-send-email-computersforpeace@gmail.com>

The `mtdinfo' utility (with the `-a' flag) is much more informative
than `cat /proc/mtd', so encourage users to use it if possible when
sending bug reports.

Signed-off-by: Brian Norris <computersforpeace@gmail.com>
---
v2: use &nbsp; within <code> tags to prevent linebreaks

 faq/ubi.xml   |    4 ++--
 faq/ubifs.xml |    4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/faq/ubi.xml b/faq/ubi.xml
index 2d9ce6e..9458e77 100644
--- a/faq/ubi.xml
+++ b/faq/ubi.xml
@@ -874,8 +874,8 @@ quicker than the first method.</p>
 	<li>provide UBI configuration from you your <code>.config</code>
 	file, or just attach whole file;</li>
 
-	<li>describe your flash device, attach the
-	"<code>cat /proc/mtd</code>" output;</li>
+	<li>describe your flash device, attach the "<code>mtdinfo&amp;nbsp;-a</code>"
+	output (or the less useful "<code>cat&amp;nbsp;/proc/mtd</code>" output);</li>
 
 	<li>specify which kernel version you are using; if your kernel is not
 	the latest one, please, explicitly tell whether you updated UBI by
diff --git a/faq/ubifs.xml b/faq/ubifs.xml
index 14043f5..dbfac0e 100644
--- a/faq/ubifs.xml
+++ b/faq/ubifs.xml
@@ -1485,8 +1485,8 @@ all checks: "<code>echo 127 > /sys/module/ubifs/parameters/debug_chks</code>".</
 	<li>provide UBIi and UBIFS configuration from you your
 	<code>.config</code> file, or just attach whole file;</li>
 
-	<li>describe your flash device, attach the
-	"<code>cat /proc/mtd</code>" output;</li>
+	<li>describe your flash device, attach the "<code>mtdinfo&amp;nbsp;-a</code>"
+	output (or the less useful "<code>cat&amp;nbsp;/proc/mtd</code>" output);</li>
 
 	<li>specify which kernel version you are using; if your kernel is not
 	the latest one, please, explicitly tell whether you updated UBIFS by
-- 
1.7.0.4

  reply	other threads:[~2011-08-09 22:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08 19:37 [PATCH 0/9] mtd-www: various fixes, bug reporting info Brian Norris
2011-08-08 19:37 ` [PATCH 1/9] UBIFS FAQ: spelling, grammar Brian Norris
2011-08-08 19:37 ` [PATCH 2/9] faq: general: update "pleonasm" description Brian Norris
2011-08-08 19:37 ` [PATCH 3/9] faq: general: turn statement into a question Brian Norris
2011-08-08 19:37 ` [PATCH 4/9] faq/doc: ubi(fs): move "bug report" questions to FAQ Brian Norris
2011-08-08 19:37 ` [PATCH 5/9] doc: nand: update YAFFS URL Brian Norris
2011-08-08 19:37 ` [PATCH 6/9] doc: update info on compiling mtd-utils Brian Norris
2011-08-08 19:37 ` [PATCH 7/9] faq: ubi(fs): sending bug reports using `mtdinfo' Brian Norris
2011-08-09 22:03   ` Brian Norris [this message]
2011-08-08 19:37 ` [PATCH 8/9] faq: ubi(fs): small spelling, URL fixups Brian Norris
2011-08-09 22:05   ` [PATCH v2 " Brian Norris
2011-08-08 19:37 ` [PATCH 9/9] faq: general: add bug reporting FAQ Brian Norris
2011-08-09  8:10   ` Brian Foster
2011-08-09 22:05   ` [PATCH v2 " Brian Norris
2011-08-10  7:54     ` Brian Foster
2011-08-10  8:34       ` [PATCH " Brian Norris
2011-08-08 20:00 ` [PATCH 0/9] mtd-www: various fixes, bug reporting info Artem Bityutskiy
2011-08-15 12:19 ` Artem Bityutskiy

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=1312927434-16708-1-git-send-email-computersforpeace@gmail.com \
    --to=computersforpeace@gmail.com \
    --cc=brian.foster@maxim-ic.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.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