From: Alexander Sverdlin <alexander.sverdlin@nsn.com>
To: ext Brian Norris <computersforpeace@gmail.com>
Cc: Joern Engel <joern@lazybastard.org>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd: phram: Make phram 64-bit compatible
Date: Tue, 08 Oct 2013 09:46:40 +0200 [thread overview]
Message-ID: <5253B860.5030604@nsn.com> (raw)
In-Reply-To: <20131007174943.GB23337@ld-irv-0074.broadcom.com>
Hi!
On 10/07/2013 07:49 PM, ext Brian Norris wrote:
> 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?
I was also irritated re-inventing the wheel here, but the problem is --
millions of people out there have their startup scripts and uboot environments
for phram, who expect this just to work with the next kernel upgrade...
--
Best regards,
Alexander Sverdlin.
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Sverdlin <alexander.sverdlin@nsn.com>
To: ext Brian Norris <computersforpeace@gmail.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: Tue, 08 Oct 2013 09:46:40 +0200 [thread overview]
Message-ID: <5253B860.5030604@nsn.com> (raw)
In-Reply-To: <20131007174943.GB23337@ld-irv-0074.broadcom.com>
Hi!
On 10/07/2013 07:49 PM, ext Brian Norris wrote:
> 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?
I was also irritated re-inventing the wheel here, but the problem is --
millions of people out there have their startup scripts and uboot environments
for phram, who expect this just to work with the next kernel upgrade...
--
Best regards,
Alexander Sverdlin.
next prev parent reply other threads:[~2013-10-08 7:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 16:42 [PATCH] mtd: phram: Make phram 64-bit compatible Alexander Sverdlin
2013-10-04 22:02 ` Jörn Engel
2013-10-07 17:49 ` Brian Norris
2013-10-07 17:49 ` Brian Norris
2013-10-07 16:53 ` Jörn Engel
2013-10-07 16:53 ` Jörn Engel
2013-10-08 16:36 ` Geert Uytterhoeven
2013-10-08 16:36 ` Geert Uytterhoeven
2013-10-08 7:46 ` Alexander Sverdlin [this message]
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=5253B860.5030604@nsn.com \
--to=alexander.sverdlin@nsn.com \
--cc=computersforpeace@gmail.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 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.