All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Schoenebeck <linux_oss@crudebyte.com>,
	Eric Van Hensbergen <ericvh@kernel.org>,
	v9fs@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [GIT PULL] 9p fixes for 6.13-rc1
Date: Sat, 30 Nov 2024 01:51:29 +0900	[thread overview]
Message-ID: <Z0nxET2etduwcfj0@codewreck.org> (raw)

The following changes since commit 2d5404caa8c7bb5c4e0435f94b28834ae5456623:

  Linux 6.12-rc7 (2024-11-10 14:19:35 -0800)

are available in the Git repository at:

  https://github.com/martinetd/linux tags/9p-for-6.13-rc1

for you to fetch changes up to e0260d530b73ee969ae971d14daa02376dcfc93f:

  net/9p/usbg: allow building as standalone module (2024-11-22 23:48:14 +0900)

----------------------------------------------------------------
9p update for 6.13-rc1

- usbg: fix alloc failure handling & build-as-module
- xen: couple of fixes
- v9fs_cache_register/unregister code cleanup

----------------------------------------------------------------
Alex Zenla (2):
      9p/xen: fix init sequence
      9p/xen: fix release of IRQ

Colin Ian King (1):
      fs/9p: replace functions v9fs_cache_{register|unregister} with direct calls

Dominique Martinet (1):
      net/9p/usbg: allow building as standalone module

Mirsad Todorovac (1):
      net/9p/usbg: fix handling of the failed kzalloc() memory allocation

 fs/9p/v9fs.c        | 21 +++------------------
 net/9p/Kconfig      |  4 ++--
 net/9p/trans_usbg.c |  4 ++--
 net/9p/trans_xen.c  |  9 ++++++---
 4 files changed, 13 insertions(+), 25 deletions(-)

--
Dominique Martinet | Asmadeus

             reply	other threads:[~2024-11-29 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29 16:51 Dominique Martinet [this message]
2024-11-30 18:39 ` [GIT PULL] 9p fixes for 6.13-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=Z0nxET2etduwcfj0@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=ericvh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=torvalds@linux-foundation.org \
    --cc=v9fs@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.