public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Luca Ellero <luca.ellero@brickedbrain.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mtd: nand: mxs: fix PIO_WORD number
Date: Tue, 10 Feb 2015 16:18:12 +0100	[thread overview]
Message-ID: <54DA2134.6030606@brickedbrain.com> (raw)
In-Reply-To: <54DA043F.1020501@denx.de>

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.
Regards
Luca


-- 
Luca Ellero

E-mail: luca.ellero at brickedbrain.com
Internet: www.brickedbrain.com

  reply	other threads:[~2015-02-10 15:18 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 [this message]
2015-02-10 15:47                       ` Marek Vasut

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=54DA2134.6030606@brickedbrain.com \
    --to=luca.ellero@brickedbrain.com \
    --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