public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] ppc4xx: Move definition for PPC4xx NAND FLASH controller to header
Date: Sat, 23 May 2009 12:47:35 +0200	[thread overview]
Message-ID: <200905231247.35836.sr@denx.de> (raw)
In-Reply-To: <4A145163.1090005@freescale.com>

On Wednesday 20 May 2009 20:52:19 Scott Wood wrote:
> > Scott, please review this patchset. It fixes a problem with the 4xx NDFC
> > and it's compatibility with the Linux driver. I would really like to get
> > this into this 2009-06 release. Since this patchset also touches a file
> > in drivers/mtd/nand, how should we handle those patches? Should I push
> > those patches (after your ACK) via my ppc4xx repository?
>
> ACK 1-3
>
> Though once we get kconfig, we should pull the ifdef out of the NAND
> code and have MTD_NAND_ECC_SMC be selected by NAND_NDFC.

Yes, I already thought about this too.

Thanks.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

      reply	other threads:[~2009-05-23 10:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20  8:58 [U-Boot] [PATCH 1/3] ppc4xx: Move definition for PPC4xx NAND FLASH controller to header Stefan Roese
2009-05-20  8:58 ` [U-Boot] [PATCH 2/3] ppc4xx: Fix problem with ECC ordering for PPC4xx NDFC platforms Stefan Roese
2009-05-20  8:58 ` [U-Boot] [PATCH 3/3] nand: " Stefan Roese
2009-05-20 18:52 ` [U-Boot] [PATCH 1/3] ppc4xx: Move definition for PPC4xx NAND FLASH controller to header Scott Wood
2009-05-23 10:47   ` Stefan Roese [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=200905231247.35836.sr@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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