public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>,
	linux-mtd@lists.infradead.org, dsd@laptop.org,
	Jamie Iles <jamie@jamieiles.com>
Subject: Re: [PATCH] mtd: cafe_nand: register master MTD at most once
Date: Mon, 15 Aug 2011 18:31:13 +0300	[thread overview]
Message-ID: <1313422279.8691.9.camel@sauron> (raw)
In-Reply-To: <1312328310-18003-1-git-send-email-computersforpeace@gmail.com>

On Tue, 2011-08-02 at 16:38 -0700, Brian Norris wrote:
> This patch addresses a regression where a master MTD object might be
> registered twice if no partitions are found. The initial bug report can
> be seen here:
>     http://lists.infradead.org/pipermail/linux-mtd/2011-July/037086.html
> 
> The regression is caused by:
>     commit 0f7451bea72c64d3f0a47850328d52f0315e2ea6
>     "mtd: cafe_nand.c: use mtd_device_parse_register"

Thanks for the fix! For some reason David missed the last merge window
and did not merge the MTD stuff. So we still have a possibility to fix
the original commit, so I folded this into commit 0f7451bea.

-- 
Best Regards,
Artem Bityutskiy

  reply	other threads:[~2011-08-15 15:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-14 17:37 MTD-related kobject badness during linux-next boot Daniel Drake
2011-08-02 17:40 ` Brian Norris
2011-08-02 17:58   ` Daniel Drake
2011-08-02 18:05     ` Brian Norris
2011-08-02 22:53   ` Jamie Iles
2011-08-02 23:38   ` [PATCH] mtd: cafe_nand: register master MTD at most once Brian Norris
2011-08-15 15:31     ` Artem Bityutskiy [this message]
2011-08-15 17:41       ` 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=1313422279.8691.9.camel@sauron \
    --to=dedekind1@gmail.com \
    --cc=computersforpeace@gmail.com \
    --cc=dbaryshkov@gmail.com \
    --cc=dsd@laptop.org \
    --cc=dwmw2@infradead.org \
    --cc=jamie@jamieiles.com \
    --cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox