Re: linux-next: Tree for Feb 24

From	Sedat Dilek <sedat.dilek@gmail.com>
Newsgroups	linux.kernel
Subject	Re: linux-next: Tree for Feb 24
Date	2016-03-17 11:30 +0100
Message-ID	<rdDlM-68F-5@gated-at.bofh.it> (permalink)
References	<r5Al4-8jS-1@gated-at.bofh.it> <r5Bh7-wo-1@gated-at.bofh.it> <r5ILE-5T6-29@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Wed, Feb 24, 2016 at 3:37 PM, Benjamin LaHaise <bcrl@kvack.org> wrote:
> On Wed, Feb 24, 2016 at 07:32:17AM +0100, Sedat Dilek wrote:
>> On Wed, Feb 24, 2016 at 6:34 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> > Hi all,
>> >
>> > Changes since 20160223:
>> >
>> ...
>> > The aio tree still had a build failure so I used the version from
>> > next-20160111.
>> >
>>
>> Might be good to poke the maintainer as I am seeing this for a long
>> time in Linux-next.
>
> These are architecture code related build failures that arch maintainers
> need to fix.  Avoiding pulling the tree allows people to ignore the issue,
> which isn't going to get things fixed.  I provided an example how to
> implement the 64 bit __get_user() without generating warnings, and it is
> now up to maintainers to adapt it for their architecture.
>

Hi Ben,

not seeing this anymore.
How was that solved?

Regards,
- Sedat -

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: linux-next: Tree for Feb 24 Sedat Dilek <sedat.dilek@gmail.com> - 2016-03-17 11:30 +0100

csiph-web