From: Christoph Hellwig <hch@lst.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org,
Russell King <rmk+kernel@armlinux.org.uk>,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] ARM: oabi-compat: fix epoll_ctl build failure
Date: Wed, 29 Apr 2020 08:28:42 +0200 [thread overview]
Message-ID: <20200429062842.GA31478@lst.de> (raw)
In-Reply-To: <20200428213747.3663311-1-arnd@arndb.de>
On Tue, Apr 28, 2020 at 11:37:30PM +0200, Arnd Bergmann wrote:
> Two functions are not declared or defined when CONFIG_EPOLL is
> disabled:
Can we just compile out the whole syscall handler and use
COND_SYSCALL_COMPAT or so?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Russell King <linux@armlinux.org.uk>,
Christoph Hellwig <hch@lst.de>,
Russell King <rmk+kernel@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: oabi-compat: fix epoll_ctl build failure
Date: Wed, 29 Apr 2020 08:28:42 +0200 [thread overview]
Message-ID: <20200429062842.GA31478@lst.de> (raw)
In-Reply-To: <20200428213747.3663311-1-arnd@arndb.de>
On Tue, Apr 28, 2020 at 11:37:30PM +0200, Arnd Bergmann wrote:
> Two functions are not declared or defined when CONFIG_EPOLL is
> disabled:
Can we just compile out the whole syscall handler and use
COND_SYSCALL_COMPAT or so?
next prev parent reply other threads:[~2020-04-29 6:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 21:37 [PATCH] ARM: oabi-compat: fix epoll_ctl build failure Arnd Bergmann
2020-04-28 21:37 ` Arnd Bergmann
2020-04-29 6:28 ` Christoph Hellwig [this message]
2020-04-29 6:28 ` Christoph Hellwig
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=20200429062842.GA31478@lst.de \
--to=hch@lst.de \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=rmk+kernel@armlinux.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 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.