From: dmitry pervushin <dpervushin@embeddedalley.com>
To: dedekind@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH, UBI] ubi notifications
Date: Wed, 29 Apr 2009 19:29:33 +0400 [thread overview]
Message-ID: <1241018973.20184.32.camel@hp.diimka.lan> (raw)
In-Reply-To: <1240644884.22645.90.camel@localhost.localdomain>
The patchset is in next three messages
On Sat, 2009-04-25 at 10:34 +0300, Artem Bityutskiy wrote:
> On Sat, 2009-04-25 at 01:39 +0400, dmitry pervushin wrote:
> > UBI volume notifications is intended to create the API to get clients
> > notified about volume creation/deletion, renaming and changing(actually,
> > resizing). A client can subscribe to these notifications using
> > ubi_volume_register and cancel the subsription using
> > ubi_volume_unregister. When UBI volume change occurs, the atomic
> > notifier will be called. Client also can request "added" event on all
> > volumes that existed before client subscribed to the notifications.
> >
> > Using notifications instead of calling functions ubi_gluebi_xxx allows
> > MTD emulation layer to be more flexible; say, now is it possible to
> > build it as a module and load/unload it on demand.
> >
> > Thanks Artem Bityutskiy for reviewing the patch and many very valuable
> > comments.
> >
> > Signed-off-by: dmitry pervushin <dpervushin@embeddedalley.com>
>
> Hi,
>
> thanks for the patch. Is it possible to submit it together
> with a user? E.g., AFAIR you separated out gluebi, could
> this be also submitted? I would be much happier to see a
> new interface functions + a user, not just the interface
> functions alone.
>
> I've inlined a slightly midified version of your patch
> for you, because I found it easier to fix minor things
> rather than request you about this.
[skipped]
prev parent reply other threads:[~2009-04-29 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 21:39 [PATCH, UBI] ubi notifications dmitry pervushin
2009-04-25 7:34 ` Artem Bityutskiy
2009-04-29 15:29 ` dmitry pervushin [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=1241018973.20184.32.camel@hp.diimka.lan \
--to=dpervushin@embeddedalley.com \
--cc=dedekind@infradead.org \
--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