From: Richard Weinberger <richard@sigma-star.at>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mtd <linux-mtd@lists.infradead.org>
Subject: [GIT PULL] UBI and UBIFS changes for v6.19-rc1
Date: Mon, 08 Dec 2025 21:15:50 +0100 [thread overview]
Message-ID: <21252217.fSG56mABFh@nailgun> (raw)
Linus,
The following changes since commit 6a23ae0a96a600d1d12557add110e0bb6e32730c:
Linux 6.18-rc6 (2025-11-16 14:25:38 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs.git tags/ubifs-for-linus-6.19-rc1
for you to fetch changes up to 0695aef23d674815c352293c49d944a2375ee9c9:
ubifs: vmalloc(array_size()) -> vmalloc_array() (2025-11-28 21:52:55 +0100)
----------------------------------------------------------------
This pull request contains the following changes for UBI and UBIFS:
UBIFS:
- Misc code cleanups such as removal of unnecessary variables
UBI:
- No longer program unused bit in UBI headers
----------------------------------------------------------------
Cheng Ming Lin (1):
mtd: ubi: skip programming unused bits in ubi headers
Liyuan Pang (1):
ubi: fastmap: fix ubi->fm memory leak
Qianfeng Rong (1):
ubifs: vmalloc(array_size()) -> vmalloc_array()
Xichao Zhao (3):
ubifs: Remove unnecessary parameters '*c'
ubifs: Simplify the code using ubifs_crc_node
ubifs: Remove unnecessary variable assignments
drivers/mtd/ubi/attach.c | 4 +++-
drivers/mtd/ubi/fastmap-wl.c | 8 +-------
drivers/mtd/ubi/io.c | 10 ++++++++++
drivers/mtd/ubi/ubi.h | 12 ++++++++++++
fs/ubifs/io.c | 13 ++++---------
fs/ubifs/lpt.c | 12 ++++++------
fs/ubifs/recovery.c | 4 +---
fs/ubifs/tnc_misc.c | 9 +--------
fs/ubifs/ubifs.h | 2 +-
9 files changed, 39 insertions(+), 35 deletions(-)
next reply other threads:[~2025-12-08 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 20:15 Richard Weinberger [this message]
2025-12-09 0:11 ` [GIT PULL] UBI and UBIFS changes for v6.19-rc1 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=21252217.fSG56mABFh@nailgun \
--to=richard@sigma-star.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