From: Dominique Martinet <asmadeus@codewreck.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net
Subject: [GIT PULL] 9p update for 5.13-rc1
Date: Fri, 7 May 2021 20:41:21 +0900 [thread overview]
Message-ID: <YJUnYXZBd1hpwW6G@codewreck.org> (raw)
Hi Linux,
sorry for the late request, this is trivial enough and should probably
not have waited for the next cycle...
I had forgotten to add a Cc to stable for the fix and didn't want to
amend the commit at the last minute, will send them a mail after this
has been merged.
The following changes since commit a5e13c6df0e41702d2b2c77c8ad41677ebb065b3:
Linux 5.12-rc5 (2021-03-28 15:48:16 -0700)
are available in the Git repository at:
https://github.com/martinetd/linux tags/9p-for-5.13-rc1
for you to fetch changes up to f8b139e2f24112f4e21f1eb02c7fc7600fea4b8d:
fs: 9p: fix v9fs_file_open writeback fid error check (2021-03-31 07:02:47 +0900)
----------------------------------------------------------------
9p for 5.13-rc1
an error handling fix and const optimization
----------------------------------------------------------------
Rikard Falkeborn (1):
9p: Constify static struct v9fs_attr_group
Yang Yingliang (1):
fs: 9p: fix v9fs_file_open writeback fid error check
fs/9p/v9fs.c | 2 +-
fs/9p/vfs_file.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
Thanks,
--
Dominique
next reply other threads:[~2021-05-07 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 11:41 Dominique Martinet [this message]
2021-05-07 19:07 ` [GIT PULL] 9p update for 5.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=YJUnYXZBd1hpwW6G@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=v9fs-developer@lists.sourceforge.net \
/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).