From: Dominique Martinet <asmadeus@codewreck.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: netdev@vger.kernel.org, v9fs-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] 9p update for 5.10-rc1
Date: Thu, 22 Oct 2020 14:08:26 +0200 [thread overview]
Message-ID: <20201022120826.GA28295@nautica> (raw)
Hi Linus,
another harmless cycle.
(sorry latest commit's message isn't great, I was half expecting a v2
but it didn't come and I remembered too late/didn't want to reword it
myself; and it's still worth taking as is)
Thanks,
The following changes since commit 549738f15da0e5a00275977623be199fbbf7df50:
Linux 5.9-rc8 (2020-10-04 16:04:34 -0700)
are available in the Git repository at:
https://github.com/martinetd/linux tags/9p-for-5.10-rc1
for you to fetch changes up to 7ca1db21ef8e0e6725b4d25deed1ca196f7efb28:
net: 9p: initialize sun_server.sun_path to have addr's value only when addr is valid (2020-10-12 10:05:47 +0200)
----------------------------------------------------------------
9p pull request for inclusion in 5.10
A couple of small fixes (loff_t overflow on 32bit, syzbot uninitialized
variable warning) and code cleanup (xen)
----------------------------------------------------------------
Anant Thazhemadam (1):
net: 9p: initialize sun_server.sun_path to have addr's value only when addr is valid
Matthew Wilcox (Oracle) (1):
9P: Cast to loff_t before multiplying
Ye Bin (1):
9p/xen: Fix format argument warning
fs/9p/vfs_file.c | 4 ++--
net/9p/trans_fd.c | 2 +-
net/9p/trans_xen.c | 4 ++--
3 files changed, 5 insertions(+), 5 deletions(-)
--
Dominique
next reply other threads:[~2020-10-22 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 12:08 Dominique Martinet [this message]
2020-10-22 16:36 ` [GIT PULL] 9p update for 5.10-rc1 Linus Torvalds
2020-10-22 18:05 ` 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=20201022120826.GA28295@nautica \
--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).