public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Shmulik Ladkani <shmulik.ladkani@gmail.com>
Cc: dwmw2@infradead.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: unify initialization of erase_info->fail_addr
Date: Mon, 13 Feb 2012 16:03:16 +0200	[thread overview]
Message-ID: <1329141796.22240.154.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1329141752.22240.153.camel@sauron.fi.intel.com>

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

On Mon, 2012-02-13 at 16:02 +0200, Artem Bityutskiy wrote:
> On Thu, 2012-02-09 at 15:36 +0200, Shmulik Ladkani wrote:
> > From: Shmulik Ladkani <shmulik.ladkani@gmail.com>
> > 
> > Initialization of 'erase_info->fail_addr' to MTD_FAIL_ADDR_UNKNOWN prior
> > erase operation is duplicated accross several MTD drivers, and also taken
> > care of by some MTD users as well.
> > 
> > Harmonize it: initialize 'fail_addr' within 'mtd_erase()' interface.
> > 
> > Signed-off-by: Shmulik Ladkani <shmulik.ladkani@gmail.com>
> 
> Could you please re-send this one and
> 
> [PATCH] sfc: mtd: Use MTD_FAIL_ADDR_UNKNOWN instead of 0xffffffff
> 
> as a single patch or a series of 2 patches?

I mean this patch should also patch 'sfc' or just contain that change,
right?

-- 
Best Regards,
Artem Bityutskiy

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

  reply	other threads:[~2012-02-13 14:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 13:36 [PATCH] mtd: unify initialization of erase_info->fail_addr Shmulik Ladkani
2012-02-13 14:02 ` Artem Bityutskiy
2012-02-13 14:03   ` Artem Bityutskiy [this message]
2012-02-13 18:56     ` Shmulik Ladkani
2012-03-21  9:09 ` Shmulik Ladkani
2012-03-21 14:08   ` Artem Bityutskiy

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=1329141796.22240.154.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --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