From: Benjamin LaHaise <bcrl@kvack.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: linux-next <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-aio@kvack.org
Subject: Re: linux-next: Tree for Feb 24
Date: Wed, 24 Feb 2016 09:37:19 -0500 [thread overview]
Message-ID: <20160224143719.GE7382@kvack.org> (raw)
In-Reply-To: <CA+icZUVeY1-HbhQChpC=vwJO7Fk+3d07UFmDxW13vaoVEUTk9g@mail.gmail.com>
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.
-ben
> - Sedat -
--
"Thought is the essence of where you are now."
next prev parent reply other threads:[~2016-02-24 14:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 5:34 linux-next: Tree for Feb 24 Stephen Rothwell
2016-02-24 6:32 ` Sedat Dilek
2016-02-24 14:37 ` Benjamin LaHaise [this message]
2016-03-17 10:21 ` Sedat Dilek
2016-03-17 10:27 ` Stephen Rothwell
2016-03-17 10:37 ` Sedat Dilek
-- strict thread matches above, loose matches on Subject: below --
2023-02-24 4:49 Stephen Rothwell
2022-02-25 2:16 broonie
2021-02-24 3:36 Stephen Rothwell
2020-02-24 4:32 Stephen Rothwell
2017-02-24 3:01 Stephen Rothwell
2015-02-24 3:02 Stephen Rothwell
2014-02-24 6:37 Stephen Rothwell
2013-02-26 3:16 Stephen Rothwell
2013-02-26 5:00 ` Sedat Dilek
2013-02-26 5:30 ` Stephen Rothwell
2012-02-24 6:05 Stephen Rothwell
2008-02-25 6:31 Stephen Rothwell
2008-02-25 10:12 ` Frank Seidel
2008-02-25 11:11 ` Stephen Rothwell
2008-02-24 5:23 Stephen Rothwell
2008-02-24 18:19 ` Kevin Winchester
2008-02-24 20:00 ` Rafael J. Wysocki
2008-02-24 23:35 ` Kevin Winchester
2008-02-24 23:43 ` Rafael J. Wysocki
2008-02-25 0:23 ` Kevin Winchester
2008-02-25 9:26 ` Pavel Machek
2008-02-25 21:56 ` Geert Uytterhoeven
2008-02-25 22:30 ` Randy Dunlap
2008-02-25 23:49 ` Stephen Rothwell
2008-02-26 7:55 ` Geert Uytterhoeven
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=20160224143719.GE7382@kvack.org \
--to=bcrl@kvack.org \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).