All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Schoenebeck <linux_oss@crudebyte.com>
To: Latchesar Ionkov <lucho@ionkov.net>,
	Dominique Martinet <asmadeus@codewreck.org>,
	Eric Van Hensbergen <ericvh@kernel.org>
Cc: v9fs@lists.linux.dev, linux-kernel@vger.kernel.org,
	kernel@pengutronix.de,
	Robert Schwebel <r.schwebel@pengutronix.de>,
	Eric Van Hensbergen <ericvh@kernel.org>
Subject: Re: [PATCH 3/3] fs/9p: fix type mismatch in file cache mode helper
Date: Tue, 18 Jul 2023 11:40:25 +0200	[thread overview]
Message-ID: <2057058.f4oLnqTvTQ@silver> (raw)
In-Reply-To: <20230716-fixes-overly-restrictive-mmap-v1-3-0683b283b932@kernel.org>

On Monday, July 17, 2023 6:29:02 PM CEST Eric Van Hensbergen wrote:
> There were two flags which had incorrect type in the
> paramaters of the file cache mode helper function.

1. typo: "parameters"

2. I would be more precise and actually name the two flags in question in the
commit log.

> Signed-off-by: Eric Van Hensbergen <ericvh@kernel.org>
> ---
>  fs/9p/fid.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/9p/fid.h b/fs/9p/fid.h
> index 297c2c377e3dd..29281b7c38870 100644
> --- a/fs/9p/fid.h
> +++ b/fs/9p/fid.h
> @@ -46,8 +46,8 @@ static inline struct p9_fid *v9fs_fid_clone(struct dentry *dentry)
>   * NOTE: these are set after open so only reflect 9p client not
>   * underlying file system on server.
>   */
> -static inline void v9fs_fid_add_modes(struct p9_fid *fid, int s_flags,
> -	int s_cache, unsigned int f_flags)
> +static inline void v9fs_fid_add_modes(struct p9_fid *fid, unsigned int s_flags,
> +	unsigned int s_cache, unsigned int f_flags)
>  {
>  	if (fid->qid.type != P9_QTFILE)
>  		return;
> 
> 





  parent reply	other threads:[~2023-07-18  9:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 16:28 [PATCH 0/3] fs/9p: fix mmap regression Eric Van Hensbergen
2023-07-17 16:29 ` [PATCH 1/3] fs/9p: remove unecessary and overrestrictive check Eric Van Hensbergen
2023-07-18  2:45   ` Dominique Martinet
2023-07-18  9:17     ` Christian Schoenebeck
2023-07-17 16:29 ` [PATCH 2/3] fs/9p: fix typo in comparison logic for cache mode Eric Van Hensbergen
2023-07-18  2:48   ` Dominique Martinet
2023-07-18  9:34     ` Christian Schoenebeck
2023-07-17 16:29 ` [PATCH 3/3] fs/9p: fix type mismatch in file cache mode helper Eric Van Hensbergen
2023-07-18  2:50   ` Dominique Martinet
2023-07-18  9:40   ` Christian Schoenebeck [this message]
2023-07-19 14:17 ` [PATCH 0/3] fs/9p: fix mmap regression Thorsten Leemhuis

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=2057058.f4oLnqTvTQ@silver \
    --to=linux_oss@crudebyte.com \
    --cc=asmadeus@codewreck.org \
    --cc=ericvh@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucho@ionkov.net \
    --cc=r.schwebel@pengutronix.de \
    --cc=v9fs@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.