From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] UBI changes for 2.6.35
Date: Thu, 20 May 2010 16:48:37 +0300 [thread overview]
Message-ID: <20100520134837.3024.89757.sendpatchset@localhost.localdomain> (raw)
Hi Linus,
please, pull the UBI tree:
The following changes since commit 01bf0b64579ead8a82e7cfc32ae44bc667e7ad0f:
Linus Torvalds (1):
Linux 2.6.34-rc5
are available in the git repository at:
git://git.infradead.org/ubi-2.6.git linux-next
Kevin Cernekee (1):
UBI: remove reboot notifier
Marc Kleine-Budde (1):
UBI: init even if MTD device cannot be attached, if built into kernel
Shinya Kuribayashi (2):
UBI: fix s/then/than/ typos
UBI: misc comment fixes
drivers/mtd/ubi/Kconfig | 2 +-
drivers/mtd/ubi/build.c | 60 ++++++++++++++++++-----------------------------
drivers/mtd/ubi/io.c | 6 ++--
drivers/mtd/ubi/kapi.c | 6 ++--
drivers/mtd/ubi/scan.c | 4 +-
drivers/mtd/ubi/ubi.h | 2 -
drivers/mtd/ubi/vtbl.c | 4 +-
drivers/mtd/ubi/wl.c | 2 +-
8 files changed, 35 insertions(+), 51 deletions(-)
Thanks,
Artem.
reply other threads:[~2010-05-20 13:50 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=20100520134837.3024.89757.sendpatchset@localhost.localdomain \
--to=artem.bityutskiy@nokia.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