mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	 linux-mtd <linux-mtd@lists.infradead.org>
Subject: [GIT PULL] JFFS2 and UBIFS fixes for v6.16-rc1
Date: Sat, 7 Jun 2025 07:59:51 +0200 (CEST)	[thread overview]
Message-ID: <1612150437.134340417.1749275991560.JavaMail.zimbra@nod.at> (raw)

Linus,

The following changes since commit 82f2b0b97b36ee3fcddf0f0780a9a0825d52fec3:

  Linux 6.15-rc6 (2025-05-11 14:54:11 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs.git tags/ubifs-for-linus-6.16-rc1

for you to fetch changes up to 2b6d96503255a3ed676cd70f8368870c6d6a25c6:

  jffs2: check jffs2_prealloc_raw_node_refs() result in few other places (2025-05-22 20:54:38 +0200)

----------------------------------------------------------------
This pull request contains the following fixes for JFFS2 and UBIFS:

JFFS2:
	- Correctly check return code of jffs2_prealloc_raw_node_refs()

UBIFS:
	- Spelling fixes

----------------------------------------------------------------
Artem Sadovnikov (1):
      jffs2: check that raw node were preallocated before writing summary

Fedor Pchelkin (1):
      jffs2: check jffs2_prealloc_raw_node_refs() result in few other places

Thorsten Blum (1):
      ubifs: Fix grammar in error message

 fs/jffs2/erase.c   | 4 +++-
 fs/jffs2/scan.c    | 4 +++-
 fs/jffs2/summary.c | 7 ++++++-
 fs/ubifs/journal.c | 2 +-
 4 files changed, 13 insertions(+), 4 deletions(-)

             reply	other threads:[~2025-06-07  6:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-07  5:59 Richard Weinberger [this message]
2025-06-07 14:39 ` Linus Torvalds
2025-06-07 14:41 ` 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=1612150437.134340417.1749275991560.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

all inboxes | Powered by JetHome®