From: David Miller <davem@davemloft.net>
To: viro@ZenIV.linux.org.uk
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Feb 22
Date: Thu, 21 Feb 2008 23:30:15 -0800 (PST) [thread overview]
Message-ID: <20080221.233015.193695196.davem@davemloft.net> (raw)
In-Reply-To: <20080222072554.GG27894@ZenIV.linux.org.uk>
From: Al Viro <viro@ZenIV.linux.org.uk>
Date: Fri, 22 Feb 2008 07:25:54 +0000
> On Fri, Feb 22, 2008 at 06:21:16PM +1100, Stephen Rothwell wrote:
> > On Fri, 22 Feb 2008 17:04:21 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > Status of my local build tests is at
> > > http://kisskb.ellerman.id.au/kisskb/branch/9/. The sparc builds have
> > > been mostly disabled while I obtain a working cross compiler.
> >
> > I have reenabled the sparc and sparc64 builds but there is a bug in 32bit
> > sparc (in Linus' tree) at the moment.
>
> Remove includes of linux/rcupdate.h and linux/mm.h from memcontrol.h;
> patch had been posted some time ago.
Yes, it's clogged up in Andrew's patch queue somewhere.
next prev parent reply other threads:[~2008-02-22 7:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 6:04 Stephen Rothwell
2008-02-22 6:32 ` Frank Seidel
2008-02-22 6:58 ` Stephen Rothwell
2008-02-22 6:43 ` Frank Seidel
2008-02-22 7:04 ` Stephen Rothwell
2008-02-22 7:21 ` Stephen Rothwell
2008-02-22 7:25 ` Al Viro
2008-02-22 7:30 ` David Miller [this message]
2008-02-23 8:04 ` Andrew Morton
2008-02-22 22:12 ` Randy Dunlap
2012-02-22 5:28 Stephen Rothwell
2013-02-22 4:28 Stephen Rothwell
2015-02-22 6:32 Stephen Rothwell
2016-02-22 7:03 Stephen Rothwell
2017-02-22 4:54 Stephen Rothwell
2018-02-22 3:37 Stephen Rothwell
2019-02-22 7:55 Stephen Rothwell
2021-02-22 9:13 Stephen Rothwell
2022-02-23 1:41 broonie
2023-02-22 3:52 Stephen Rothwell
2024-02-22 11:49 Stephen Rothwell
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=20080221.233015.193695196.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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
Powered by JetHome