From: "Bityutskiy, Artem" <artem.bityutskiy@intel.com>
To: "alexander.stein@systec-electronic.com"
<alexander.stein@systec-electronic.com>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v2 1/1] mtd: mtdram: Add parameter for setting writebuf size
Date: Wed, 2 Mar 2016 14:35:55 +0000 [thread overview]
Message-ID: <1456929355.2169.24.camel@intel.com> (raw)
In-Reply-To: <1456929164.2169.21.camel@gmail.com>
On Wed, 2016-03-02 at 16:32 +0200, Artem Bityutskiy wrote:
> On Wed, 2016-03-02 at 14:06 +0100, Alexander Stein wrote:
> >
> > +config MTDRAM_WRITEBUF_SIZE
> > + int "MTDRAM write buf size in Bytes"
> > + depends on MTD_MTDRAM
> > + default "64"
> > + help
> > + This allows you to configure the write buffer size in the
> > device
> > + emulated by the MTDRAM driver. If the MTDRAM driver is
> > built
> > + as a module, it is also possible to specify this as a
> > parameter when
> > + loading the module. E.g. ubifs relies this in the
> > recovery
> > algorithm.
> Why another Kconfig option (compile-time) instead of just a module
> parameter (run-time), which would be more flexible?
Oh, pardon, you are adding both. I never found the Kconfig options very
useful. Quite the opposite, I always thought MTD has too many of those
little Kconfig options and the config menu is too large. I'd suggest to
only add the runtime option, unless you really need the Kconfig option
too (why?).
--
Best Regards,
Artem Bityutskiy
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next prev parent reply other threads:[~2016-03-02 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 13:06 [PATCH v2 1/1] mtd: mtdram: Add parameter for setting writebuf size Alexander Stein
2016-03-02 14:32 ` Artem Bityutskiy
2016-03-02 14:35 ` Bityutskiy, Artem [this message]
2016-03-02 14:48 ` Alexander Stein
2016-03-02 14:54 ` Bityutskiy, Artem
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=1456929355.2169.24.camel@intel.com \
--to=artem.bityutskiy@intel.com \
--cc=alexander.stein@systec-electronic.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).