linux-kernel - [GIT PULL] UBIFS changes for 3.12-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <1379316587.17490.56.camel@sauron.fi.intel.com>
Date:	Mon, 16 Sep 2013 10:29:47 +0300
From:	Artem Bityutskiy <dedekind1@...il.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-mtd <linux-mtd@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: [GIT PULL] UBIFS changes for 3.12-rc1

Hi Linus,

very few changes. I'll start using a single UBI/UBIFS tree instead
of 2 trees from now on. So in the future you'll get 1 small pull
request instead of 2 tiny ones.

The following changes since commit d4e4ab86bcba5a72779c43dc1459f71fea3d89c8:

  Linux 3.11-rc5 (2013-08-11 18:04:20 -0700)

are available in the git repository at:

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

for you to fetch changes up to c23e9b75ccd0edba81a506c7d97e0af626489256:

  UBIFS: remove invalid warn msg with tst_recovery enabled (2013-08-16 16:42:08 +0300)

----------------------------------------------------------------
Just one patch which fixes the power-cut recovery testing mode.

----------------------------------------------------------------
Mats Kärrman (1):
      UBIFS: remove invalid warn msg with tst_recovery enabled

 fs/ubifs/debug.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

-- 
Best Regards,
Artem Bityutskiy

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/