From: "Bityutskiy, Artem" <artem.bityutskiy@intel.com>
To: "alexander.stein@systec-electronic.com"
<alexander.stein@systec-electronic.com>
Cc: "computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"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:54:30 +0000 [thread overview]
Message-ID: <1456930470.2169.26.camel@intel.com> (raw)
In-Reply-To: <38372465.103Wx4k7xg@ws-stein>
On Wed, 2016-03-02 at 15:48 +0100, Alexander Stein wrote:
> I don't need it. Setting using modprobe is enough for me and a lot
> more flexible. I just kept it the same way as the other 2 parameters.
> Even those are rather useless in Kconfig, IMHO. Or do you prefer
> removing the existing Kconfig options all together and just rely on
> module parameters?
I'd recommend to avoid expanding the Kconfig, which is already complex
and quite confusing for someone who is not an MTD expert but just tries
to come up with a reasonable default Kconfig (e.g., and distro
builder).
--
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.
prev parent reply other threads:[~2016-03-02 14:54 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
2016-03-02 14:48 ` Alexander Stein
2016-03-02 14:54 ` Bityutskiy, Artem [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=1456930470.2169.26.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).