From: Richard Weinberger <richard@nod.at>
To: torvalds <torvalds@linux-foundation.org>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] UBI/UBIFS fixes for 5.7 final
Date: Wed, 20 May 2020 21:49:38 +0200 (CEST) [thread overview]
Message-ID: <294087931.249343.1590004178869.JavaMail.zimbra@nod.at> (raw)
Linus,
The following changes since commit c0cc271173b2e1c2d8d0ceaef14e4dfa79eefc0d:
Merge tag 'modules-for-v5.7' of git://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux (2020-04-09 12:52:34 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs.git tags/for-linus-5.7-rc6
for you to fetch changes up to 0e7572cffe442290c347e779bf8bd4306bb0aa7c:
ubi: Fix seq_file usage in detailed_erase_block_info debugfs file (2020-05-17 23:38:21 +0200)
----------------------------------------------------------------
This pull request contains the following bug fixes for UBI and UBIFS:
- Correctly set next cursor for detailed_erase_block_info debugfs file
- Don't use crypto_shash_descsize() for digest size in UBIFS
- Remove broken lazytime support from UBIFS
----------------------------------------------------------------
Christoph Hellwig (1):
ubifs: remove broken lazytime support
Eric Biggers (1):
ubifs: fix wrong use of crypto_shash_descsize()
Richard Weinberger (1):
ubi: Fix seq_file usage in detailed_erase_block_info debugfs file
drivers/mtd/ubi/debug.c | 12 ++----------
fs/ubifs/auth.c | 17 ++++-------------
fs/ubifs/file.c | 6 +-----
fs/ubifs/replay.c | 13 ++-----------
4 files changed, 9 insertions(+), 39 deletions(-)
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2020-05-20 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 19:49 Richard Weinberger [this message]
2020-05-20 20:30 ` [GIT PULL] UBI/UBIFS fixes for 5.7 final pr-tracker-bot
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=294087931.249343.1590004178869.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--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;
as well as URLs for NNTP newsgroup(s).