linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Scott Wood <scottwood@freescale.com>,
	David Woodhouse <dwmw2@infradead.org>,
	linux-mtd@lists.infradead.org,
	Shmulik Ladkani <shmulik.ladkani@gmail.com>
Subject: Re: [PATCH 1/3] mtd: nandsim: remove autoincrement code
Date: Wed, 02 May 2012 12:57:42 +0300	[thread overview]
Message-ID: <1335952662.10293.37.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1335917575-14953-1-git-send-email-computersforpeace@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 438 bytes --]

On Tue, 2012-05-01 at 17:12 -0700, Brian Norris wrote:
> The NAND layer always has NAND_NO_AUTOINCR set, so we will never utilize the
> AUTOINCR code in nandsim. We will be removing the NAND_NO_AUTOINCR option soon,
> and so kill this code as well.
> 
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>

Pushed to l2-mtd.git, thanks.

P.S. Jumped at your patches to unblock you.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2012-05-02  9:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  0:12 [PATCH 1/3] mtd: nandsim: remove autoincrement code Brian Norris
2012-05-02  0:12 ` [PATCH 2/3] mtd: nand: remove autoincrement 'sndcmd' code Brian Norris
2012-05-03  6:17   ` Shmulik Ladkani
2012-05-03 10:39     ` Artem Bityutskiy
2012-05-02  0:12 ` [PATCH 3/3] mtd: nand: kill NAND_NO_AUTOINCR option Brian Norris
2012-05-02  9:57 ` Artem Bityutskiy [this message]
2012-05-02 17:22   ` [PATCH 1/3] mtd: nandsim: remove autoincrement code Brian Norris

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=1335952662.10293.37.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=scottwood@freescale.com \
    --cc=shmulik.ladkani@gmail.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;
as well as URLs for NNTP newsgroup(s).