All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] omap: pandora: fix NAND support
Date: Mon, 13 Jun 2011 06:49:43 -0700	[thread overview]
Message-ID: <20110613134943.GF3352@atomide.com> (raw)
In-Reply-To: <1307132643-17432-1-git-send-email-notasas@gmail.com>

* Grazvydas Ignotas <notasas@gmail.com> [110603 13:20]:
> Commit d5ce2b65 "omap3630: nand: fix device size to work in polled mode"
> changed values for .devsize in nand platform data, now we have to pass
> NAND_BUSWIDTH_16 instead of '1' to select 16bit NAND.
> 
> Update pandora's platform data accordingly, also specify appropriate
> transfer type.

Thanks adding to fixes.

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] omap: pandora: fix NAND support
Date: Mon, 13 Jun 2011 06:49:43 -0700	[thread overview]
Message-ID: <20110613134943.GF3352@atomide.com> (raw)
In-Reply-To: <1307132643-17432-1-git-send-email-notasas@gmail.com>

* Grazvydas Ignotas <notasas@gmail.com> [110603 13:20]:
> Commit d5ce2b65 "omap3630: nand: fix device size to work in polled mode"
> changed values for .devsize in nand platform data, now we have to pass
> NAND_BUSWIDTH_16 instead of '1' to select 16bit NAND.
> 
> Update pandora's platform data accordingly, also specify appropriate
> transfer type.

Thanks adding to fixes.

Tony

  reply	other threads:[~2011-06-13 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03 20:24 [PATCH] omap: pandora: fix NAND support Grazvydas Ignotas
2011-06-03 20:24 ` Grazvydas Ignotas
2011-06-13 13:49 ` Tony Lindgren [this message]
2011-06-13 13:49   ` Tony Lindgren

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=20110613134943.GF3352@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=notasas@gmail.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 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.