From: Bernd Schubert <bschubert@ddn.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Miklos Szeredi <miklos@szeredi.hu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tags need some work in the fuse tree
Date: Thu, 23 Jan 2025 23:35:53 +0100 [thread overview]
Message-ID: <42938a54-de82-4eee-a338-ce57f3ca4c7d@ddn.com> (raw)
In-Reply-To: <20250124071333.6d91cfc2@canb.auug.org.au>
Hi Stephen,
On 1/23/25 21:13, Stephen Rothwell wrote:
> 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
yes sorry, as I wrote in the introduction mail, as
linux-next gets rebases (I think) - didn't know what to put in.
And Miklos might wrap these into the existing patches.
Will do with SHAs from 'current' linux-next next time and also
send a v2 in the morning.
Thanks,
Bernd
prev parent reply other threads:[~2025-01-23 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 20:13 linux-next: Fixes tags need some work in the fuse tree Stephen Rothwell
2025-01-23 22:35 ` Bernd Schubert [this message]
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=42938a54-de82-4eee-a338-ce57f3ca4c7d@ddn.com \
--to=bschubert@ddn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=sfr@canb.auug.org.au \
/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