public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: dpervushin@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [UBI] 0/4 notifications
Date: Tue, 09 Dec 2008 12:36:21 +0200	[thread overview]
Message-ID: <1228818981.13686.171.camel@sauron> (raw)
In-Reply-To: <1228759154.7622.26.camel@hp.diimka.lan>

On Mon, 2008-12-08 at 20:59 +0300, dmitry pervushin wrote:
> I am glad to present the serie of patches that implement volume
> notifications in UBI and based on these notifications reworked MTD
> emulation layer and a simple mtdblock-like FTL.
> 
> 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.
> 
> The simple FTL uses the same notification mechanism and provides
> mtdblock-like layer.

Hi,

minor general notes:

1. Please, make sure checkpatch.pl is happy - here are complaints about
trailing white-spaces.

2. Would you please add kernel-doc style comments functions you
introduce? Lets maintain consistent code style please.

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

      reply	other threads:[~2008-12-09 10:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08 17:59 [PATCH] [UBI] 0/4 notifications dmitry pervushin
2008-12-09 10:36 ` 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=1228818981.13686.171.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=dpervushin@gmail.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