From: Brian Norris <computersforpeace@gmail.com>
To: Alexander Sverdlin <alexander.sverdlin@nsn.com>
Cc: linux-mtd@lists.infradead.org,
Joern Engel <joern@lazybastard.org>,
David Woodhouse <dwmw2@infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd: phram: Make phram 64-bit compatible
Date: Mon, 7 Oct 2013 10:49:43 -0700 [thread overview]
Message-ID: <20131007174943.GB23337@ld-irv-0074.broadcom.com> (raw)
In-Reply-To: <524C4CF5.7060601@nsn.com>
+ LKML
On Wed, Oct 02, 2013 at 06:42:29PM +0200, Alexander Sverdlin wrote:
> mtd: phram: Make phram 64-bit compatible
>
> phram was 32-bit limited by design. Machines are growing up, but phram
> module is still useful. Update it. The patch is bigger than minimum,
> because simple_strtoul() is obsolete.
>
> Tested on MIPS64 and compile-tested for PPC (32 bit).
>
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@nsn.com>
Pushed to l2-mtd.git. Thanks!
Can this driver use the library memparse() function instead of
open-coding it?
[To answer myself:] I noticed this in drivers/mtd/devices/phram.c, which
prevents us from using memparse():
/* By dwmw2 editorial decree, "ki", "Mi" or "Gi" are to be used. */
Are we (MTD) holding a revolutionary position against the standard
kernel libraries, which recognize [KkMmGg] prefixes, but not [kMG]i
prefixes? Should we extend memparse() to accept either form? Or would
doing so simply pollute the library and not really satisfy anyone?
[After more research:] It looks like this topic may be the subject of
some long-past flame wars. If I am digging up past demons, then I'd
prefer to let sleeping Balrogs lie.
Brian
next parent reply other threads:[~2013-10-07 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <524C4CF5.7060601@nsn.com>
2013-10-07 17:49 ` Brian Norris [this message]
2013-10-07 16:53 ` Jörn Engel
2013-10-08 16:36 ` Geert Uytterhoeven
2013-10-08 7:46 ` Alexander Sverdlin
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=20131007174943.GB23337@ld-irv-0074.broadcom.com \
--to=computersforpeace@gmail.com \
--cc=alexander.sverdlin@nsn.com \
--cc=dwmw2@infradead.org \
--cc=joern@lazybastard.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®