public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: dpervushin@embeddedalley.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] 3/3 ubi notification API Re: [PATCH] [UBI] [1/3] ubi notifications API
Date: Sun, 31 May 2009 17:06:42 +0300	[thread overview]
Message-ID: <1243778802.11172.140.camel@localhost.localdomain> (raw)
In-Reply-To: <1243625251.4067.29.camel@hp.diimka.lan>

On Fri, 2009-05-29 at 23:27 +0400, dmitry pervushin wrote:
> On Mon, 2009-05-18 at 18:39 +0300, Artem Bityutskiy wrote:
> > On Mon, 2009-05-18 at 18:22 +0300, Artem Bityutskiy wrote:
> > > Dmitry,
> > > 
> > > I've re-work the first patch of yours. I think the locking should
> > > be correct now. The commit message shortly list the changes I've
> > > done.
> > > 
> > > I also send the second patch. The only thing I fixed there was
> > > the spelling of your name - I made it start with a capital letter.
> > > I hope you do not mind.
> > > 
> > > Please, provide the third patch. You should not try to open an
> > > UBI volume from within a notifier, because it won't work. I
> > > think you simply did not test your patches before sending.
> > > Neither did I. But please, this time, do test the patches.
> > > It is very easy to do with nansim.
> > > 
> > > I'll send the patches as 2 follow-up e-mail for your review.
> > 
> > I've also created an "experimental" branch in the ubi-2.6.git
> > tree for your convenience:
> > 
> > http://git.infradead.org/ubi-2.6.git?a=shortlog;h=refs/heads/experimental
> > git://git.infradead.org/ubi-2.6.git experimental
> Sorry for late response; I reviewed your changes, and although
> prohibiting of using ubi api from within notifiers does not look very
> amazing to me... but it seems that it is the only robust way. The 3rd
> patch from the serie is inlined below (tested on the stmp378x board as
> well as on nandsim)

Well. I assume that:

1. when gluebi is notified, it creates its data structures without
   opening the UBI volume;
2. when a gluebi /dev/mtdX device is being opened, the the corresponding
   UBI volume is opened as well.

At least for gluebi's purposes it seems to be enough. Recursions are
painful and I would keep things simple, unless we have more complex
use-cases where we would have to invent something trickier.

But anyway, AFAIR I re-named many constants and strictures in your
original patces to make them a bit more consistent/shorter. But your new
patch N.3 does not seem to be against those 2 patches I sent you (and
also put to the "experimental" branch).

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

      parent reply	other threads:[~2009-05-31 14:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29 15:29 [PATCH] [UBI] [1/3] ubi notifications API dmitry pervushin
2009-05-06  6:31 ` Artem Bityutskiy
2009-05-07  6:14 ` Artem Bityutskiy
2009-05-18  8:05 ` Artem Bityutskiy
2009-05-18 15:22 ` Artem Bityutskiy
2009-05-18 15:26   ` [PATCH] UBI: add notification API Artem Bityutskiy
2009-05-18 15:28     ` [PATCH] UBI: remove built-in gluebi Artem Bityutskiy
2009-05-18 15:39   ` [PATCH] [UBI] [1/3] ubi notifications API Artem Bityutskiy
2009-05-29 19:27     ` [PATCH] 3/3 ubi notification API " dmitry pervushin
2009-05-31 13:52       ` Artem Bityutskiy
2009-05-31 14:32         ` [PATCH] 3/3 ubi notification API (was Re: [PATCH] [UBI] [1/3] ubi notifications API) dmitry pervushin
2009-06-01 16:48           ` Artem Bityutskiy
2009-06-01 17:07             ` dmitry pervushin
2009-06-02  6:40               ` Artem Bityutskiy
2009-05-31 14:06       ` Artem Bityutskiy [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=1243778802.11172.140.camel@localhost.localdomain \
    --to=dedekind@infradead.org \
    --cc=dpervushin@embeddedalley.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