From: "Bityutskiy, Artem" <artem.bityutskiy@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
Linux Kernel Maling List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] UBI/UBIFS fixes for 3.5-rc2
Date: Fri, 8 Jun 2012 17:07:20 +0000 [thread overview]
Message-ID: <1339175470.2392.6.camel@sauron.fi.intel.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1208 bytes --]
The following changes since commit f8f5701bdaf9134b1f90e5044a82c66324d2073f:
Linux 3.5-rc1 (2012-06-02 18:29:26 -0700)
are available in the git repository at:
git://git.infradead.org/linux-ubifs.git tags/upstream-3.5-rc2
for you to fetch changes up to 12027f1b3fd69a4e9017e6b13c72547a99c6cf54:
UBI: correct ubi_wl_flush locking (2012-06-07 15:22:21 +0300)
----------------------------------------------------------------
Fix UBI and UBIFS - they refuse to work without debugfs. This was
broken by the 3.5-rc1 UBI/UBIFS changes when we removed the debugging
Kconfig switches.
Also, correct locking in 'ubi_wl_flush()' - it was extended to support
flushing a specific LEB in 3.5-rc1, and the locking was sub-optimal.
----------------------------------------------------------------
Artem Bityutskiy (3):
UBI: fix debugfs-less systems support
UBIFS: fix debugfs-less systems support
UBI: correct ubi_wl_flush locking
drivers/mtd/ubi/debug.c | 12 ++++++++++--
drivers/mtd/ubi/wl.c | 17 +++++++++++++----
fs/ubifs/debug.c | 12 ++++++++++--
3 files changed, 33 insertions(+), 8 deletions(-)
--
Best Regards,
Artem Bityutskiy
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 464 bytes --]
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
reply other threads:[~2012-06-08 17:07 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=1339175470.2392.6.camel@sauron.fi.intel.com \
--to=artem.bityutskiy@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).