All of lore.kernel.org
 help / color / mirror / Atom feed
From: Huang Shijie <b32955@freescale.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org,
	stable@vger.kernel.org, festevam@gmail.com, dedekind1@gmail.com
Subject: Re: [PATCH 1/2] mtd: gpmi: fix the NULL pointer
Date: Mon, 11 Nov 2013 17:30:20 +0800	[thread overview]
Message-ID: <5280A3AC.4020305@freescale.com> (raw)
In-Reply-To: <20131108175119.GA20061@ld-irv-0074.broadcom.com>

于 2013年11月09日 01:51, Brian Norris 写道:
> Thanks for looking into this quickly, BTW.
this patch is not good, it uses the data in the stack to do the DMA 
transfer.

I will send a new patch to fix this NULL issue.

thanks
Huang Shijie

  parent reply	other threads:[~2013-11-11  9:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07  9:46 [PATCH 1/2] mtd: gpmi: fix the NULL pointer Huang Shijie
2013-11-07  9:46 ` [PATCH 2/2] mtd: gpmi: only scan two chips for imx6 Huang Shijie
2013-11-07 13:08   ` Fabio Estevam
2013-11-08  3:11     ` Huang Shijie
2013-11-08  3:14       ` Huang Shijie
2013-11-07 13:22   ` Fabio Estevam
2013-11-08  3:26     ` Huang Shijie
2013-11-08 18:44   ` Brian Norris
2013-11-07 13:07 ` [PATCH 1/2] mtd: gpmi: fix the NULL pointer Fabio Estevam
2013-11-08  3:10   ` Huang Shijie
2013-11-08 12:49     ` Fabio Estevam
2013-11-08 17:51 ` Brian Norris
2013-11-08 21:01   ` Fabio Estevam
2013-11-09 18:10   ` Huang Shijie
2013-11-11  9:30   ` Huang Shijie [this message]
2013-11-11 10:40   ` [PATCH V2] " Huang Shijie
2013-11-11 11:07     ` Huang Shijie
2013-11-11 12:41       ` Fabio Estevam
2013-11-11 17:07     ` Fabio Estevam
2013-11-12  3:18     ` Brian Norris
     [not found]       ` <5281A058.1080501@freescale.com>
2013-11-12  4:27         ` Brian Norris
2013-11-12  3:20     ` Huang Shijie

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=5280A3AC.4020305@freescale.com \
    --to=b32955@freescale.com \
    --cc=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=festevam@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=stable@vger.kernel.org \
    /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.