mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gao Xiang <xiang@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-erofs@lists.ozlabs.org, LKML <linux-kernel@vger.kernel.org>,
	Sheng Yong <shengyong1@xiaomi.com>, Bo Liu <liubo03@inspur.com>,
	Chao Yu <chao@kernel.org>
Subject: [GIT PULL] erofs fixes for 6.15-rc2
Date: Mon, 14 Apr 2025 01:03:42 +0800	[thread overview]
Message-ID: <Z/vubg+MYaiszHm2@debian> (raw)

Hi Linus,

Could you consider those fixes for 6.15-rc2?

Just a few miscellaneous fixes as shown below..  All commits have been
in -next for a while and no potential merge conflicts is observed.

Thanks,
Gao Xiang

The following changes since commit 0af2f6be1b4281385b618cb86ad946eded089ac8:

  Linux 6.15-rc1 (2025-04-06 13:11:33 -0700)

are available in the Git repository at:

   git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-6.15-rc2-fixes

for you to fetch changes up to f5ffef9881a76764477978c39f1ad0136a4adcab:

  erofs: remove duplicate code (2025-04-10 14:24:05 +0800)

----------------------------------------------------------------
Changes since last update:

 - Properly handle errors when file-backed I/O fails.

 - Fix compilation issues on ARM platform (arm-linux-gnueabi);

 - Fix parsing of encoded extents;

 - Minor cleanup.

----------------------------------------------------------------
Bo Liu (1):
      erofs: remove duplicate code

Gao Xiang (2):
      erofs: add __packed annotation to union(__le16..)
      erofs: fix encoded extents handling

Sheng Yong (1):
      erofs: set error to bio if file-backed IO fails

 fs/erofs/erofs_fs.h | 8 ++++----
 fs/erofs/fileio.c   | 2 ++
 fs/erofs/zdata.c    | 1 -
 fs/erofs/zmap.c     | 5 +++--
 4 files changed, 9 insertions(+), 7 deletions(-)

             reply	other threads:[~2025-04-13 17:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-13 17:03 Gao Xiang [this message]
2025-04-13 18:24 ` 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=Z/vubg+MYaiszHm2@debian \
    --to=xiang@kernel.org \
    --cc=chao@kernel.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liubo03@inspur.com \
    --cc=shengyong1@xiaomi.com \
    --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®