From: Artem Bityutskiy <dedekind1@gmail.com>
To: Richard Genoud <richard.genoud@gmail.com>
Cc: linux-mtd@lists.infradead.org,
Shmulik Ladkani <shmulik.ladkani@gmail.com>
Subject: Re: [PATCH v3 4/6] UBI: replace MTD_UBI_BEB_LIMIT with module parameter
Date: Tue, 21 Aug 2012 16:54:55 +0300 [thread overview]
Message-ID: <1345557295.2848.112.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1345478416-23900-5-git-send-email-richard.genoud@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
Amended the commit subject,
On Mon, 2012-08-20 at 18:00 +0200, Richard Genoud wrote:
> This patch provides the possibility to adjust the "maximum expected number of
> bad blocks per 1024 blocks" (max_beb_per1024) for each mtd device.
>
> The majority of NAND devices have their max_beb_per1024 equal to 20, but
> sometimes it's more.
> Now, we can adjust that via a kernel parameter:
> ubi.mtd=<name|num|path>[,<vid_hdr_offs>[,max_beb_per1024]]
>
> Signed-off-by: Richard Genoud <richard.genoud@gmail.com>
Did few minor amendments and applied this one. And pushed out.
> + pr_err("UBI error: bad value for max_beb_per1024 parameter: %s",
> + tokens[2]);
Changed this to 'printk(KERN_ERR' and wrapped the line.
The former is because the entire function uses 'printk(KERN_ERR', and I
am a fan of consistency. We can change them all to 'pr_err()' and
'pr_warn()' in a separate patch.
Similar for wrapping - UBI wraps all messages. If we want, we can unwrap
them all in a separate patch.
Feel free to submit such a patch, I won't have objections.
> -MODULE_PARM_DESC(mtd, "MTD devices to attach. Parameter format: "
> - "mtd=<name|num|path>[,<vid_hdr_offs>].\n"
You unwrapped this one and I pushed that as is, because it is just much
more readable, and it is the only place where we describe a module, so
no inconsistencies. :-)
Thank you!
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-21 13:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 16:00 [PATCH v3 0/6] UBI: add max_beb_per1024 parameter / ioctl Richard Genoud
2012-08-20 16:00 ` [PATCH v3 1/6] UBI: prepare for max_beb_per1024 module parameter addition Richard Genoud
2012-08-20 19:01 ` Artem Bityutskiy
2012-08-20 16:00 ` [PATCH v3 2/6] UBI: change CONFIG_MTD_UBI_BEB_LIMIT range Richard Genoud
2012-08-20 19:03 ` Artem Bityutskiy
2012-08-20 16:00 ` [PATCH v3 3/6] UBI: check max_beb_per1024 value in ubi_attach_mtd_dev Richard Genoud
2012-08-20 19:19 ` Artem Bityutskiy
2012-08-20 16:00 ` [PATCH v3 4/6] UBI: replace MTD_UBI_BEB_LIMIT with module parameter Richard Genoud
2012-08-21 13:54 ` Artem Bityutskiy [this message]
2012-08-22 8:32 ` Richard Genoud
2012-08-22 8:49 ` Artem Bityutskiy
2012-08-22 12:09 ` Richard Genoud
2012-08-22 12:16 ` Artem Bityutskiy
2012-08-20 16:00 ` [PATCH v3 5/6] UBI: add ioctl for max_beb_per1024 Richard Genoud
2012-08-21 19:34 ` Artem Bityutskiy
2012-08-20 16:00 ` [PATCH v3 6/6] UBI: drop CONFIG_MTD_UBI_BEB_LIMIT Richard Genoud
2012-08-21 19:34 ` Artem Bityutskiy
2012-08-23 10:10 ` [PATCH v3 0/6] UBI: add max_beb_per1024 parameter / ioctl Artem Bityutskiy
2012-08-23 10:36 ` Shmulik Ladkani
2012-08-23 11:01 ` Richard Genoud
2012-08-23 12:30 ` Artem Bityutskiy
2012-08-23 12:44 ` Shmulik Ladkani
2012-08-23 12:58 ` Artem Bityutskiy
2012-08-23 13:13 ` Richard Genoud
2012-08-23 14:45 ` Artem Bityutskiy
2012-08-31 14:46 ` Richard Genoud
2012-09-03 8:00 ` Artem Bityutskiy
2012-09-03 10:57 ` Richard Genoud
2012-09-03 11:53 ` Artem Bityutskiy
2012-09-03 13:14 ` Richard Genoud
2012-09-03 13:31 ` Artem Bityutskiy
2012-09-03 13:37 ` Richard Genoud
2012-09-03 14:32 ` Artem Bityutskiy
2012-09-03 14:33 ` Artem Bityutskiy
2012-09-03 14:45 ` Richard Genoud
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=1345557295.2848.112.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.genoud@gmail.com \
--cc=shmulik.ladkani@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.