From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Bernd Schubert <bschubert@ddn.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tags need some work in the fuse tree
Date: Fri, 24 Jan 2025 07:13:33 +1100 [thread overview]
Message-ID: <20250124071333.6d91cfc2@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]
Hi all,
In commit
d76c8bb7e031 ("fuse: Fix the struct fuse_args->in_args array size")
Fixes tag
Fixes: fuse: make args->in_args[0] to be always the header
has these problem(s):
- No SHA1 recognised
Maybe you meant:
Fixes: e24b7a3b70ae ("fuse: make args->in_args[0] to be always the header")
In commit
a5564ff833b7 ("fuse: Remove unneeded include in fuse_dev_i.h")
Fixes tag
Fixes: fuse: {io-uring} Make hash-list req unique finding functions non-static
has these problem(s):
- No SHA1 recognised
Maybe you meant:
Fixes: 543282def3fc ("fuse: {io-uring} Make hash-list req unique finding functions non-static")
In commit
f571aa60acaa ("fuse: Remove an err= assignment and move a comment")
Fixes tag
Fixes: fuse: {io-uring} Handle SQEs - register commands
has these problem(s):
- No SHA1 recognised
Maybe you meant:
Fixes: d7c8f3c02e21 ("fuse: {io-uring} Handle SQEs - register commands")
In commit
3a0d08c113a3 ("fuse: Fix copy_from_user error return code in fuse_uring_commit")
Fixes tag
Fixes: fuse: Add io-uring sqe commit and fetch support
has these problem(s):
- No SHA1 recognised
Maybe you meant:
Fixes: d5223c566a20 ("fuse: Add io-uring sqe commit and fetch support")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-01-23 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 20:13 Stephen Rothwell [this message]
2025-01-23 22:35 ` linux-next: Fixes tags need some work in the fuse tree Bernd Schubert
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=20250124071333.6d91cfc2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bschubert@ddn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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