From: Walter Harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Cc: Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
linux-um@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hostfs: fix mismatch between link_file definition and declaration
Date: Mon, 18 Mar 2019 09:46:44 +0100 (CET) [thread overview]
Message-ID: <430554945.231221.1552898805187@ox-groupware.bfs.de> (raw)
Hi,
Colin is obvously right with that.
But my guess is that the error occured because the
pattern (from, to) is brocken here. Also
Maybe the maintainer can fix that.
just my 2 cents,
re,
wh
Am 18.03.2019 00:09, schrieb Colin King:
> From: Colin Ian King <colin.king@canonical.com>
>
> The function link_file declaration in the header file has the order
> of the two arguments (from, to) swapped when compared to the definition
> arguments of (to, from). Fix this by swapping them around to match
> the definition.
>
> This error predates the git history, so no idea when this error
> was introduced.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> fs/hostfs/hostfs.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/hostfs/hostfs.h b/fs/hostfs/hostfs.h
> index 33b8423ef0c9..f4295aa19350 100644
> --- a/fs/hostfs/hostfs.h
> +++ b/fs/hostfs/hostfs.h
> @@ -87,7 +87,7 @@ extern int do_mkdir(const char *file, int mode);
> extern int hostfs_do_rmdir(const char *file);
> extern int do_mknod(const char *file, int mode, unsigned int major,
> unsigned int minor);
> -extern int link_file(const char *from, const char *to);
> +extern int link_file(const char *to, const char *from);
> extern int hostfs_do_readlink(char *file, char *buf, int size);
> extern int rename_file(char *from, char *to);
> extern int rename2_file(char *from, char *to, unsigned int flags);
next reply other threads:[~2019-03-18 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 8:46 Walter Harms [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-17 23:09 [PATCH] hostfs: fix mismatch between link_file definition and declaration Colin King
2019-03-17 23:49 ` Richard Weinberger
2019-03-18 8:41 ` Colin Ian King
2019-03-18 9:30 ` Richard Weinberger
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=430554945.231221.1552898805187@ox-groupware.bfs.de \
--to=wharms@bfs.de \
--cc=anton.ivanov@cambridgegreys.com \
--cc=jdike@addtoit.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
/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