linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd: devices: added the 16mb winbond device
Date: Mon, 13 May 2013 10:15:08 +0300	[thread overview]
Message-ID: <1368429308.5360.6.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <516d0c68.e10b420a.287d.ffff894c@mx.google.com>

On Tue, 2013-04-16 at 14:01 +0530, girishks2000 at gmail.com wrote:
> From: Girish K S <ks.giri@samsung.com>
> 
> added a 16mb winbond devce to the device list
> erase size = 64k and number of blocks = 256
> 
> Signed-off-by: Girish K S <ks.giri@samsung.com>

Pushed to l2-mtd.git, but please, remember to use better suffixes. E.g.,
mb may mean mega bytes, or mega bits. 16MiB device, 64KiB block size is
a lot less ambiguous way communicate the sizes.

I've amended your commit message.

-- 
Best Regards,
Artem Bityutskiy

      reply	other threads:[~2013-05-13  7:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16  8:31 [PATCH] mtd: devices: added the 16mb winbond device girishks2000 at gmail.com
2013-05-13  7:15 ` Artem Bityutskiy [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=1368429308.5360.6.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=linux-arm-kernel@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).