public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Linus <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
	"boris.brezillon" <boris.brezillon@free-electrons.com>
Subject: [GIT PULL] UBI/UBIFS changes for v4.16
Date: Mon, 22 Jan 2018 15:11:29 +0100	[thread overview]
Message-ID: <1676165.UvfiLElynS@blindfold> (raw)

Linus,

Sorry, I'm a week too early. Since I'm on vacation for the next two weeks
I'm sending the PR for UBI/UBIFS now and ask you to queue it until next
week (or as soon the merge window opens).

Thanks,
//richard

The following changes since commit a8750ddca918032d6349adbf9a4b6555e7db20da:

  Linux 4.15-rc8 (2018-01-14 15:32:30 -0800)

are available in the git repository at:

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

for you to fetch changes up to 7f29ae9f977bcdc3654e68bc36d170223c52fd48:

  ubi: block: Fix locking for idr_alloc/idr_remove (2018-01-18 16:48:31 +0100)

----------------------------------------------------------------
This pull request contains updates for both UBI and UBIFS:
- Usage of new fscrypt APIs
- A fix for a Fastmap issue
- Other minor bug fixes

----------------------------------------------------------------
Bradley Bolen (1):
      ubi: block: Fix locking for idr_alloc/idr_remove

Clay McClure (1):
      ubi: Fix race condition between ubi volume creation and udev

Colin Ian King (1):
      ubi: fastmap: Clean up the initialization of pointer p

Eric Biggers (5):
      ubifs: switch to fscrypt_file_open()
      ubifs: switch to fscrypt_prepare_link()
      ubifs: switch to fscrypt_prepare_rename()
      ubifs: switch to fscrypt_prepare_lookup()
      ubifs: switch to fscrypt_prepare_setattr()

Geert Uytterhoeven (1):
      ubifs: Fix uninitialized variable in search_dh_cookie()

Jeff Westfahl (1):
      mtd: ubi: Use 'max_bad_blocks' to compute bad_peb_limit if available

Pan Bian (1):
      ubi: fastmap: Use kmem_cache_free to deallocate memory

Rock Lee (1):
      ubifs: remove error message in ubifs_xattr_get

Sascha Hauer (3):
      ubi: fastmap: Erase outdated anchor PEBs during attach
      ubi: Fastmap: Fix typo
      ubi: Fix copy/paste error in function documentation

Wei Yongjun (1):
      mtd: ubi: wl: Fix error return code in ubi_wl_init()

 drivers/mtd/ubi/block.c      | 42 +++++++++++++--------
 drivers/mtd/ubi/build.c      | 13 ++++++-
 drivers/mtd/ubi/eba.c        |  2 +-
 drivers/mtd/ubi/fastmap-wl.c |  2 +-
 drivers/mtd/ubi/fastmap.c    |  5 +--
 drivers/mtd/ubi/vmt.c        | 15 +++++---
 drivers/mtd/ubi/wl.c         | 87 ++++++++++++++++++++++++++++++++------------
 drivers/mtd/ubi/wl.h         |  2 +-
 fs/ubifs/dir.c               | 43 +++++++---------------
 fs/ubifs/file.c              | 41 ++-------------------
 fs/ubifs/tnc.c               | 21 ++++-------
 fs/ubifs/xattr.c             |  2 -
 12 files changed, 140 insertions(+), 135 deletions(-)

                 reply	other threads:[~2018-01-22 14:10 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=1676165.UvfiLElynS@blindfold \
    --to=richard@nod.at \
    --cc=boris.brezillon@free-electrons.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