mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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/UBIFS updates 3.19-rc1
Date: Fri, 12 Dec 2014 18:24:00 +0200	[thread overview]
Message-ID: <1418401440.30433.20.camel@sauron.fi.intel.com> (raw)

Hi Linus,

The following changes since commit 0df1f2487d2f0d04703f142813d53615d62a1da4:

  Linux 3.18-rc3 (2014-11-02 15:01:51 -0800)

are available in the git repository at:

  git://git.infradead.org/linux-ubifs.git tags/upstream-3.19-rc1

for you to fetch changes up to f38aed975c0c3645bbdfc5ebe35726e64caaf588:

  UBI: Fix invalid vfree() (2014-11-07 15:14:09 +0200)

----------------------------------------------------------------
This pull request includes the following UBI/UBIFS changes:
* UBI debug messages now include the UBI device number. This change
  is responsible for the big diffstat since it touched every debugging
  print statement.
* An Xattr bug-fix which fixes SELinux support
* Several error path fixes in UBI/UBIFS

----------------------------------------------------------------
Artem Bityutskiy (1):
      UBIFS: fix budget leak in error path

Richard Weinberger (3):
      UBI: vtbl: Use ubi_eba_atomic_leb_change()
      UBI: Fix double free after do_sync_erase()
      UBI: Fix invalid vfree()

Subodh Nijsure (1):
      UBIFS: fix a couple bugs in UBIFS xattr length calculation

Tanya Brokhman (1):
      UBI: Extend UBI layer debug/messaging capabilities

 drivers/mtd/ubi/attach.c  | 126 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------------------------------------------------
 drivers/mtd/ubi/block.c   |  41 ++++++++++++++++++++---------------------
 drivers/mtd/ubi/build.c   | 126 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-----------------------------------------------------------
 drivers/mtd/ubi/cdev.c    |  36 +++++++++++++++++++-----------------
 drivers/mtd/ubi/debug.c   |  10 +++++-----
 drivers/mtd/ubi/eba.c     |  53 +++++++++++++++++++++++++++--------------------------
 drivers/mtd/ubi/fastmap.c |  96 ++++++++++++++++++++++++++++++++++++++++++++++++------------------------------------------------
 drivers/mtd/ubi/io.c      | 150 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------------------------------------------------------------
 drivers/mtd/ubi/kapi.c    |   6 +++---
 drivers/mtd/ubi/misc.c    |   4 ++--
 drivers/mtd/ubi/ubi.h     |  13 +++++++------
 drivers/mtd/ubi/upd.c     |  10 ++++++----
 drivers/mtd/ubi/vmt.c     |  69 ++++++++++++++++++++++++++++++++++++---------------------------------
 drivers/mtd/ubi/vtbl.c    |  71 ++++++++++++++++++++++++++++++++++-------------------------------------
 drivers/mtd/ubi/wl.c      |  80 ++++++++++++++++++++++++++++++++++++++++++--------------------------------------
 fs/ubifs/file.c           |   1 +
 fs/ubifs/journal.c        |   7 ++++++-
 17 files changed, 466 insertions(+), 433 deletions(-)

--
Artem


                 reply	other threads:[~2014-12-12 16:24 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=1418401440.30433.20.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

Powered by JetHome