From: Artem Bityutskiy <dedekind1@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] UBI changes for 3.11-rc1
Date: Fri, 05 Jul 2013 17:57:03 +0300 [thread overview]
Message-ID: <1373036223.2711.62.camel@sauron.fi.intel.com> (raw)
Hello Linus!
The following changes since commit f722406faae2d073cc1d01063d1123c35425939e:
Linux 3.10-rc1 (2013-05-11 17:14:08 -0700)
are available in the git repository at:
git://git.infradead.org/linux-ubi.git tags/upstream-3.11-rc1
for you to fetch changes up to 83ff59a066637a6c28844bbf43009459408240f4:
UBI: support ubi_num on mtd.ubi command line (2013-07-01 08:32:57 +0300)
----------------------------------------------------------------
A couple of fixes and clean-ups, allow for assigning user-defined
UBI device numbers when attaching MTD devices by using the "mtd="
module parameter.
----------------------------------------------------------------
Brian Pomerantz (1):
UBI: fastmap break out of used PEB search
Mike Frysinger (4):
UBI: drop redundant "UBI error" string
UBI: do not abort init when ubi.mtd devices cannot be found
UBI: document UBI_IOCVOLUP better in user header
UBI: support ubi_num on mtd.ubi command line
drivers/mtd/ubi/build.c | 59 ++++++++++++++++++++++++++++++++++++++++-------------------
drivers/mtd/ubi/fastmap.c | 4 +++-
include/uapi/mtd/ubi-user.h | 5 ++++-
--
Best Regards,
Artem Bityutskiy
next reply other threads:[~2013-07-05 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 14:57 Artem Bityutskiy [this message]
2013-07-05 19:12 ` [GIT PULL] UBI changes for 3.11-rc1 Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2013-07-05 14:51 Bityutskiy, Artem
2013-07-05 14:59 ` 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=1373036223.2711.62.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.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