From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Holger Brunck <holger.brunck@keymile.com>,
Anatolij Gustschin <agust@denx.de>,
Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] UBI fix for 2.6.38-rc2
Date: Sat, 29 Jan 2011 18:44:48 +0200 [thread overview]
Message-ID: <20110129164448.22944.90815.sendpatchset@localhost.localdomain> (raw)
Hi Linus,
please pull a fix for UBIFS backward compatibility breakage.
The fix consists of one revert and fixes the problem reported
here: http://lists.infradead.org/pipermail/linux-mtd/2011-January/033790.html
The following changes since commit 1bae4ce27c9c90344f23c65ea6966c50ffeae2f5:
Linux 2.6.38-rc2 (2011-01-21 19:01:34 -0800)
are available in the git repository at:
git://git.infradead.org/ubi-2.6.git for-linus
Artem Bityutskiy (1):
Revert "UBI: use mtd->writebufsize to set minimal I/O unit size"
drivers/mtd/ubi/build.c | 28 +---------------------------
1 files changed, 1 insertions(+), 27 deletions(-)
Thanks,
Artem.
reply other threads:[~2011-01-29 16:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110129164448.22944.90815.sendpatchset@localhost.localdomain \
--to=artem.bityutskiy@nokia.com \
--cc=agust@denx.de \
--cc=holger.brunck@keymile.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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