From: Brian Norris <computersforpeace@gmail.com>
To: dedekind1@gmail.com
Cc: David Clark <dclark@tantalus.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: FW: UBIFS tools and latest 2.6.33 kernel from http://git.infradead.org/users/dedekind/ubifs-v2.6.33.git
Date: Sun, 02 Sep 2012 23:05:37 -0700 [thread overview]
Message-ID: <504448B1.4050205@gmail.com> (raw)
In-Reply-To: <1346583467.2533.1.camel@kyv>
On 09/02/2012 03:57 AM, Artem Bityutskiy wrote:
> On Fri, 2012-08-31 at 15:18 -0700, Brian Norris wrote:
>> There was a series of 'writebufsize' fixes that may be missing from
>> multiple backport trees. I can help you track them down, if you'd like
>> the help.
>
> Sure, go ahead, I can them put them to the backport trees.
OK, I just put up my own github backport tree, with branches for v2.6.32
through v3.3. I think your v3.4+ repos are fine. URL:
git://github.com/computersforpeace/UBIFS-backports.git
https://github.com/computersforpeace/UBIFS-backports.git
Branches:
ubifs-v2.6.32
ubifs-v2.6.33
ubifs-v2.6.34
ubifs-v2.6.35
ubifs-v2.6.36
ubifs-v2.6.37
ubifs-v2.6.38
ubifs-v2.6.39
ubifs-v3.0
ubifs-v3.1
ubifs-v3.2
ubifs-v3.3
Each branch should have some version (amended when necessary) of the
following commits. Note that docg3 wasn't merged until v3.2. Also,
spear_smi wasn't merged until v3.4 and was already fixed in the
appropriate backports, so it is omitted from this list.
Brian
---
[ In 'git log' order ]
commit c4cc625ea5958d065c21cc0fcea29e9ed8f3d2bc
Author: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Date: Fri Feb 3 10:16:50 2012 +0200
mtd: sst25l: initialize writebufsize
commit fcc44a07dae0af16e84e93425fc8afe642ddc603
Author: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Date: Fri Feb 3 09:53:28 2012 +0200
mtd: lart: initialize writebufsize
commit 82c4c58d6f1a78e8de875272a19ab9220b8066aa
Author: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Date: Fri Feb 3 09:44:32 2012 +0200
mtd: docg3: initialize writebufsize
commit 71f60fbebf0f18dd4e855335a009efda251b1697
Author: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Date: Fri Feb 3 09:43:14 2012 +0200
mtd: doc2001plus: initialize writebufsize
commit cca84b569ebe3372b28949e00b0a3a17f87e2970
Author: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Date: Fri Feb 3 09:42:39 2012 +0200
mtd: doc2001: initialize writebufsize
commit cd1986a3c111f7ed597619705290fa52a975014f
Author: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Date: Fri Feb 3 09:38:43 2012 +0200
mtd: doc2000: initialize writebufsize
commit b604387411ec6a072e95910099262616edd2bd2f
Author: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Date: Fri Feb 3 09:32:44 2012 +0200
mtd: block2mtd: initialize writebufsize
commit b54f47c8bcfc5f766bf13ec31bd7dd1d4726d33b
Author: Brian Norris <computersforpeace@gmail.com>
Date: Tue Jan 31 00:06:03 2012 -0800
mtd: m25p80: set writebufsize
next prev parent reply other threads:[~2012-09-03 6:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 19:39 FW: UBIFS tools and latest 2.6.33 kernel from http://git.infradead.org/users/dedekind/ubifs-v2.6.33.git David Clark
2012-08-31 12:27 ` Artem Bityutskiy
2012-08-31 22:18 ` Brian Norris
2012-09-02 10:57 ` Artem Bityutskiy
2012-09-03 6:05 ` Brian Norris [this message]
2012-09-04 7:47 ` Artem Bityutskiy
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=504448B1.4050205@gmail.com \
--to=computersforpeace@gmail.com \
--cc=dclark@tantalus.com \
--cc=dedekind1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.