From: Christoph Hellwig <hch@lst.de>
To: viro@zeniv.linux.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] compat: move strut compat_iovec out of #ifdef CONFIG_COMPAT
Date: Fri, 2 Oct 2020 08:15:12 +0200 [thread overview]
Message-ID: <20201002061512.GA9230@lst.de> (raw)
In-Reply-To: <20200928161414.642727-1-hch@lst.de>
ping? This is needed to unbreak the work.iov_iter branch that is in
for-next.
On Mon, Sep 28, 2020 at 06:14:14PM +0200, Christoph Hellwig wrote:
> This avoid annoying ifdefs in iov_iter.c
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>
> This fixes a build failure with the import_iovec / compat_import_iovec
> unification.
>
> include/linux/compat.h | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/include/linux/compat.h b/include/linux/compat.h
> index 80b9b8cc1cd405..3e3d2beafed312 100644
> --- a/include/linux/compat.h
> +++ b/include/linux/compat.h
> @@ -91,6 +91,11 @@
> static inline long __do_compat_sys##name(__MAP(x,__SC_DECL,__VA_ARGS__))
> #endif /* COMPAT_SYSCALL_DEFINEx */
>
> +struct compat_iovec {
> + compat_uptr_t iov_base;
> + compat_size_t iov_len;
> +};
> +
> #ifdef CONFIG_COMPAT
>
> #ifndef compat_user_stack_pointer
> @@ -248,11 +253,6 @@ typedef struct compat_siginfo {
> } _sifields;
> } compat_siginfo_t;
>
> -struct compat_iovec {
> - compat_uptr_t iov_base;
> - compat_size_t iov_len;
> -};
> -
> struct compat_rlimit {
> compat_ulong_t rlim_cur;
> compat_ulong_t rlim_max;
> --
> 2.28.0
---end quoted text---
next prev parent reply other threads:[~2020-10-02 6:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 16:14 [PATCH] compat: move strut compat_iovec out of #ifdef CONFIG_COMPAT Christoph Hellwig
2020-10-02 6:15 ` Christoph Hellwig [this message]
2020-10-03 4:08 ` Al Viro
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=20201002061512.GA9230@lst.de \
--to=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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