public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Konstantin Tokarev <annulen@yandex.ru>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: linux-mtd@lists.infradead.org
Subject: Backporting ubiblock to Linux 3.3
Date: Tue, 15 Sep 2015 15:31:12 +0300	[thread overview]
Message-ID: <1659571442320272@web21h.yandex.ru> (raw)

Hi Ezequiel and others,

How do you think, would it be feasible to backport ubiblock to Linux 3.3 without large amount of work? I don't need latest and greatest version, just anything to get working and stable squashfs on top of it.

Could you point me to any specific version of ubiblock patch to start from? Should I apply patches from [1] first? Or any specific patches to UBI or MTD which are missing in that branch?

Thank you in advance.

[1] http://git.infradead.org/users/dedekind/ubifs-v3.3.git

-- 
Regards,
Konstantin

             reply	other threads:[~2015-09-15 12:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15 12:31 Konstantin Tokarev [this message]
2015-09-15 14:01 ` Backporting ubiblock to Linux 3.3 Richard Weinberger
2015-09-15 14:26 ` 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=1659571442320272@web21h.yandex.ru \
    --to=annulen@yandex.ru \
    --cc=ezequiel.garcia@free-electrons.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