All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mtd: nand: mxs: fix PIO_WORD number
Date: Tue, 10 Feb 2015 16:47:43 +0100	[thread overview]
Message-ID: <201502101647.43477.marex@denx.de> (raw)
In-Reply-To: <54DA2134.6030606@brickedbrain.com>

On Tuesday, February 10, 2015 at 04:18:12 PM, Luca Ellero wrote:
> On 10/02/2015 14:14, Stefano Babic wrote:
> > Hi Luca,
> > 
> > On 16/12/2014 09:06, Luca Ellero wrote:
> >>>> Scheduling the patch for -next it's ok for me.
> >>>> However there are other two points where pio_words number doesn't
> >>>> reflect the pio_words really initiated, one is in mxs_nand_read_buf()
> >>>> and one is in mxs_nand_write_buf(). Each one declares 4 pio_words but
> >>>> only one is initiated.
> >>>> I wonder what we should do in this cases.
> >>> 
> >>> You can fix those as well. I recall that all this goop came from the
> >>> original
> >>> (2.6.35) GPMI NAND driver, which is likely where all those bugs came
> >>> from as
> >>> well.
> >>> 
> >>> Thank you!
> >> 
> >> OK, I will send a patch to fix them.
> > 
> > Do you plan to send a V2 patch for fixing all the issues at once ?
> > 
> > Best regards,
> > Stefano Babic
> 
> Hi Stefano,
> yes, I can send a patch with all the fixes, that's fine.
> I plan to send it tomorrow.

Thank you :)

Best regards,
Marek Vasut

      reply	other threads:[~2015-02-10 15:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10  8:24 [U-Boot] [PATCH] mtd: nand: mxs: fix PIO_WORD number Luca Ellero
2014-12-12  8:43 ` Stefan Roese
2014-12-12 12:40   ` Luca Ellero
2014-12-12 12:43     ` Stefan Roese
2014-12-12 12:58       ` Marek Vasut
2014-12-12 15:03         ` Luca Ellero
2014-12-13 13:12           ` Marek Vasut
2014-12-15  8:45             ` Luca Ellero
2014-12-15 11:14               ` Marek Vasut
2014-12-16  8:06                 ` Luca Ellero
2014-12-16 11:45                   ` Marek Vasut
2015-02-10 13:14                   ` Stefano Babic
2015-02-10 15:18                     ` Luca Ellero
2015-02-10 15:47                       ` Marek Vasut [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=201502101647.43477.marex@denx.de \
    --to=marex@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 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.