public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Simon Kagstrom <simon.kagstrom@netinsight.net>
Cc: linux-mtd@lists.infradead.org,
	"Edgar E. Iglesias" <edgar.iglesias@axis.com>
Subject: Re: [PATCH v2, Repost]: NAND: Add panic_write for NAND flashes
Date: Thu, 08 Oct 2009 08:15:58 +0300	[thread overview]
Message-ID: <1254978958.3359.20.camel@localhost> (raw)
In-Reply-To: <20091005155552.3f2e89b8@marrow.netinsight.se>

On Mon, 2009-10-05 at 15:55 +0200, Simon Kagstrom wrote:
> This is a quick and dirty patch to add panic_write for NAND flashes. The
> patch seems to work OK on my CRIS board running a 2.6.26 kernel with a
> ID: 0x20, Chip ID: 0xf1 (ST Micro NAND 128MiB 3,3V 8-bit), and also on a
> OpenRD base (Marvell Kirkwood) board with a Toshiba NAND 512MiB 3,3V
> 8-bit flash with 2.6.32-pre1.
> 
> Signed-off-by: Edgar E. Iglesias <edgar@axis.com>
> Signed-off-by: Simon Kagstrom <simon.kagstrom@netinsight.net>
> ---
> ChangeLog:
> v2: Fix issues from Artem
>   * Fix comments about 400ms and question marks
>   * Add oops_in_progress to panic_nand_wait condition
>   * Change prototype for panic_nand_get_device
>   * Make some changes to the patch description

I've pushed this to my l2-mtd-2.6 tree, thanks:

http://git.infradead.org/users/dedekind/l2-mtd-2.6.git/commit/af9fcfdbb514e9d7e15c3b398669af1d0e714837

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

      reply	other threads:[~2009-10-08  5:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091001140959.60364dbe@marrow.netinsight.se>
     [not found] ` <20091002101431.GI9644@edde.se.axis.com>
2009-10-05 13:55   ` [PATCH v2, Repost]: NAND: Add panic_write for NAND flashes Simon Kagstrom
2009-10-08  5: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=1254978958.3359.20.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=edgar.iglesias@axis.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=simon.kagstrom@netinsight.net \
    /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