From: Artem Bityutskiy <dedekind@infradead.org>
To: Richard Purdie <rpurdie@openedhand.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Linux mtd <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] Allow variable block sizes in mtd_blkdevs
Date: Fri, 27 Oct 2006 11:52:54 +0300 [thread overview]
Message-ID: <1161939174.3080.3.camel@sauron> (raw)
In-Reply-To: <1161936573.5019.55.camel@localhost.localdomain>
Hi Richard,
On Fri, 2006-10-27 at 09:09 +0100, Richard Purdie wrote:
> Currently, mtd_blkdevs enforces a block size of 512, even if the drivers
> can seemingly request a different size. This patch fixes mtd_blkdevs so
> block sizes other than 512 work correctly.
>
> Signed-off-by: Richard Purdie <rpurdie@openedhand.com>
Looks OK for me.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2006-10-27 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 8:09 [PATCH] Allow variable block sizes in mtd_blkdevs Richard Purdie
2006-10-27 8:52 ` Artem Bityutskiy [this message]
2006-10-27 13:22 ` David Woodhouse
2006-10-30 16:37 ` Richard Purdie
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=1161939174.3080.3.camel@sauron \
--to=dedekind@infradead.org \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rpurdie@openedhand.com \
/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