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 15:47:40 +0300 [thread overview]
Message-ID: <1410180460.10764.163.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20140908111832.GA1676@arch.hh.imgtec.org>
On Mon, 2014-09-08 at 08:18 -0300, Ezequiel Garcia wrote:
> Regarding -stable, I think it's worth to pull the whole series.
I've checked and the patches do not apply to 3.16 with many conflicts.
Are you enthusiastic enough to try this and fined out the missing
dependencies?
The we could add the "Cc: stable@vger.kernel.org # v3.16+" tags, and
also mentioned the commits we depend on in the commit messages.
At this point I pushed your patches to the master branch. If you are
going to check the stable story, please, use this branch.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2014-09-08 12:48 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
2014-09-08 11:18 ` Ezequiel Garcia
2014-09-08 12:47 ` Artem Bityutskiy [this message]
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=1410180460.10764.163.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