From: Dominique Martinet <asmadeus@codewreck.org>
To: torvalds@linux-foundation.org
Cc: v9fs@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [GIT PULL] fs/9p: cleanups for 6.9-rc3
Date: Fri, 5 Apr 2024 20:30:16 +0900 [thread overview]
Message-ID: <Zg_gyHsrkjDiz7lR@codewreck.org> (raw)
Sorry, I should have sent these back for rc1. There's nothing that could
break in there and the kdoc cleanup patch caused some trouble with -next
and another identical commit, merging something should help a bit...
FYI there's some regression with the cache rework that came in rc1, if
we don't figure something out by next week it might make sense to revert
some of these; I unfortunately couldn't reproduce Kent's report but will
try a bit harder this weekend.
These commits have nothing to do with that and won't conflict.
--------
The following changes since commit 841c35169323cd833294798e58b9bf63fa4fa1de:
Linux 6.8-rc4 (2024-02-11 12:18:13 -0800)
are available in the Git repository at:
https://github.com/martinetd/linux tags/9p-for-6.9-rc3
for you to fetch changes up to 2a0505cdd8c8b12670f4b5a6eb5c996c0861c2d5:
9p: remove SLAB_MEM_SPREAD flag usage (2024-03-04 22:04:32 +0900)
----------------------------------------------------------------
minor 9p cleanups:
- kernel doc fix & removal of unused flag
- some bogus debug statement for read/write
----------------------------------------------------------------
Chengming Zhou (1):
9p: remove SLAB_MEM_SPREAD flag usage
Dominique Martinet (1):
9p: Fix read/write debug statements to report server reply
Randy Dunlap (1):
9p/trans_fd: remove Excess kernel-doc comment
fs/9p/v9fs.c | 2 +-
net/9p/client.c | 10 +++++-----
net/9p/trans_fd.c | 1 -
3 files changed, 6 insertions(+), 7 deletions(-)
Thanks,
--
Dominique Martinet | Asmadeus
next reply other threads:[~2024-04-05 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 11:30 Dominique Martinet [this message]
2024-04-05 17:09 ` [GIT PULL] fs/9p: cleanups for 6.9-rc3 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=Zg_gyHsrkjDiz7lR@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).