From: Arnd Bergmann <arnd@arndb•de>
To: linuxppc-dev@lists•ozlabs.org
Cc: Andy Shevchenko <andy.shevchenko@gmail•com>,
Stephen Rothwell <sfr@canb•auug.org.au>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
Benjamin LaHaise <bcrl@kvack•org>,
linux-next <linux-next@vger•kernel.org>,
Christoph Hellwig <hch@lst•de>, Al Viro <viro@zeniv•linux.org.uk>,
Sudip Mukherjee <sudipm.mukherjee@gmail•com>
Subject: Re: linux-next: build failure after merge of the aio tree
Date: Wed, 16 Mar 2016 14:59:38 +0100 [thread overview]
Message-ID: <4892345.flKnDo9XDS@wuerfel> (raw)
In-Reply-To: <CAHp75VcxkBTSKY_bVg3jaUPUtcyxKZ14sbu=uJK403xRmTYbbQ@mail.gmail.com>
On Wednesday 16 March 2016 13:12:36 Andy Shevchenko wrote:
>
> > I've also sent a patch that fixes the link error on ARM and that should
> > work on all other architectures too.
>
> In case of avr32 signalfd_read() fails. Does your patch help with it as well?
>
> P.S. Bisecting shows same culprit: 150a0b4905f1 ("aio: add support for
> async openat()")
I don't know. What is the symptom on avr32? My patch only removes the
get_user() instances on 64-bit values and replaces them with a
single copy_from_user() call.
Arnd
next prev parent reply other threads:[~2016-03-16 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 6:46 linux-next: build failure after merge of the aio tree Stephen Rothwell
2016-03-15 14:38 ` Andy Shevchenko
2016-03-15 16:42 ` Arnd Bergmann
2016-03-15 16:19 ` Sudip Mukherjee
2016-03-15 16:22 ` Benjamin LaHaise
2016-03-15 22:02 ` Arnd Bergmann
2016-03-16 11:12 ` Andy Shevchenko
2016-03-16 13:59 ` Arnd Bergmann [this message]
2016-03-16 14:07 ` Benjamin LaHaise
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=4892345.flKnDo9XDS@wuerfel \
--to=arnd@arndb$(echo .)de \
--cc=andy.shevchenko@gmail$(echo .)com \
--cc=bcrl@kvack$(echo .)org \
--cc=hch@lst$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sudipm.mukherjee@gmail$(echo .)com \
--cc=viro@zeniv$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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