public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Rostislav Lisovy <lisovy@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Tony Lindgren <tony@atomide.com>, Roger Quadros <rogerq@ti.com>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
	michal.vokac@comap.cz, sojkam1@fel.cvut.cz,
	Rostislav Lisovy <lisovy@merica.cz>
Subject: Re: [PATCH v2 1/2] mtd: nand: omap: Do not use global variables
Date: Wed, 22 Oct 2014 01:34:56 -0700	[thread overview]
Message-ID: <20141022083456.GF16128@brian-ubuntu> (raw)
In-Reply-To: <1412252173-20454-1-git-send-email-lisovy@merica.cz>

On Thu, Oct 02, 2014 at 02:16:12PM +0200, Rostislav Lisovy wrote:
> Since the commit 97a288ba2cfa ("ARM: omap2+: gpmc-nand: Use
> dynamic platform_device_alloc()") gpmc-nand driver supports
> multiple NAND flash devices connected to the single controller.
> Remove global variable to make the code thread-safe.
> 
> Signed-off-by: Rostislav Lisovy <lisovy@merica.cz>
> ---
> Changes since v1:
> * Do not dynamically allocate the 'struct nand_ecclayout' but rather
>   include it in the 'struct omap_nand_info' (Roger Quadros)

Pushed to l2-mtd.git with some small changes to the comment.

Thanks,
Brian

      parent reply	other threads:[~2014-10-22  8:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02 12:16 [PATCH v2 1/2] mtd: nand: omap: Do not use global variables Rostislav Lisovy
2014-10-02 12:16 ` [PATCH v2 2/2] mtd: nand: omap: Synchronize access to the ECC engine Rostislav Lisovy
2014-10-02 12:51   ` Roger Quadros
2014-10-02 13:20     ` Rostislav Lisovy
2014-10-02 12:35 ` [PATCH v2 1/2] mtd: nand: omap: Do not use global variables Roger Quadros
2014-10-02 14:16   ` [PATCH v3 2/2] mtd: nand: omap: Synchronize the access to the ECC engine Rostislav Lisovy
2014-10-29  9:16     ` Rostislav Lisovy
2014-10-29  9:24     ` Frans Klaver
2014-10-29  9:37       ` Roger Quadros
2014-10-22  8:34 ` Brian Norris [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=20141022083456.GF16128@brian-ubuntu \
    --to=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lisovy@gmail.com \
    --cc=lisovy@merica.cz \
    --cc=michal.vokac@comap.cz \
    --cc=rogerq@ti.com \
    --cc=sojkam1@fel.cvut.cz \
    --cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox