From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: "Brian Norris" <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org,
"Guido Martínez" <guido@vanguardiasur.com.ar>
Subject: Re: [PATCH 2/3] UBI: block: Add support for the UBI_VOLUME_UPDATED notification
Date: Mon, 08 Sep 2014 13:54:17 +0300 [thread overview]
Message-ID: <1410173657.10764.148.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1409348550-27768-3-git-send-email-ezequiel.garcia@free-electrons.com>
On Fri, 2014-08-29 at 18:42 -0300, Ezequiel Garcia wrote:
> Static volumes can change its 'used_bytes' when they get updated,
> and so the block interface must listen to the UBI_VOLUME_UPDATED
> notification to resize the block device accordingly.
>
> Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Looks like a good fix. If you want this in stable, you please, let me
know and also make sure you actually tested it and verified that block
device size actually gets changed.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2014-09-08 10:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 21:42 [PATCH 0/3] UBI: block: Some fixes for static volumes Ezequiel Garcia
2014-08-29 21:42 ` [PATCH 1/3] UBI: block: Fix block device size setting Ezequiel Garcia
2014-09-08 10:52 ` Artem Bityutskiy
2014-08-29 21:42 ` [PATCH 2/3] UBI: block: Add support for the UBI_VOLUME_UPDATED notification Ezequiel Garcia
2014-09-08 10:54 ` Artem Bityutskiy [this message]
2014-09-08 11:18 ` Ezequiel Garcia
2014-09-08 12:47 ` Artem Bityutskiy
2014-09-08 18:27 ` Ezequiel Garcia
2014-09-16 15:15 ` Artem Bityutskiy
2014-09-16 15:23 ` Artem Bityutskiy
2014-09-16 15:32 ` Ezequiel Garcia
2014-09-16 15:35 ` Ezequiel Garcia
2014-09-16 15:53 ` Artem Bityutskiy
2014-09-16 15:56 ` Ezequiel Garcia
2014-09-16 16:04 ` Artem Bityutskiy
2014-08-29 21:42 ` [PATCH 3/3] UBI: Dispatch update notification if the volume is updated Ezequiel Garcia
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=1410173657.10764.148.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=guido@vanguardiasur.com.ar \
--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