Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@cjr.nz>
To: Zhang Xiaoxu <zhangxiaoxu5@huawei.com>,
	linux-cifs@vger.kernel.org, zhangxiaoxu5@huawei.com,
	sfrench@samba.org, lsahlber@redhat.com, sprasad@microsoft.com,
	rohiths@microsoft.com, smfrench@gmail.com
Subject: Re: [PATCH -next 0/2] add release callback to cifs_writedata
Date: Tue, 23 Aug 2022 14:57:17 -0300	[thread overview]
Message-ID: <87zgfuhmgy.fsf@cjr.nz> (raw)
In-Reply-To: <20220823130637.1164764-1-zhangxiaoxu5@huawei.com>

Zhang Xiaoxu <zhangxiaoxu5@huawei.com> writes:

> The release function of struct cifs_writedata is determined when its
> allocated, so add it to the struct and remove the extra parameter about
> async_writev
>
> Zhang Xiaoxu (2):
>   cifs: Add release function to cifs_writedata
>   cifs: remove the release parameter form async_writev
>
>  fs/cifs/cifsglob.h  |  4 ++--
>  fs/cifs/cifsproto.h |  9 +++----
>  fs/cifs/cifssmb.c   |  5 ++--
>  fs/cifs/file.c      | 58 +++++++++++++++++++++++----------------------
>  fs/cifs/smb2pdu.c   |  5 ++--
>  fs/cifs/smb2proto.h |  3 +--
>  6 files changed, 42 insertions(+), 42 deletions(-)

Acked-by: Paulo Alcantara (SUSE) <pc@cjr.nz>

      parent reply	other threads:[~2022-08-23 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 13:06 [PATCH -next 0/2] add release callback to cifs_writedata Zhang Xiaoxu
2022-08-23 13:06 ` [PATCH -next 1/2] cifs: Add release function " Zhang Xiaoxu
2022-08-23 13:06 ` [PATCH -next 2/2] cifs: remove the release parameter form async_writev Zhang Xiaoxu
2022-08-23 17:57 ` Paulo Alcantara [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=87zgfuhmgy.fsf@cjr.nz \
    --to=pc@cjr.nz \
    --cc=linux-cifs@vger.kernel.org \
    --cc=lsahlber@redhat.com \
    --cc=rohiths@microsoft.com \
    --cc=sfrench@samba.org \
    --cc=smfrench@gmail.com \
    --cc=sprasad@microsoft.com \
    --cc=zhangxiaoxu5@huawei.com \
    /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