From: Christoph Lameter <cl@linux.com>
To: Sedat Dilek <sedat.dilek@googlemail.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Theodore Tso <tytso@mit.edu>,
sandeen@redhat.com
Subject: Re: linux-next: build failure after merge of the slab tree
Date: Tue, 8 Feb 2011 11:44:45 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.00.1102081144170.15931@router.home> (raw)
In-Reply-To: <AANLkTi=Hykzpb+oK7HOXJCCNwpgRRbsJNuXz-2Uc9WbB@mail.gmail.com>
On Tue, 8 Feb 2011, Sedat Dilek wrote:
> Isn't the fs/ext4 part obsolete by Eric's "ext4: make grpinfo slab
> cache names static"?
> The mentionned patch is pending in ext4.git#{master, for_linus} [1].
>
> Shouldn't this patch reduced to the mm/slab part?
If Eric fixed it with string constants then we do not need the slab part
either.
next prev parent reply other threads:[~2011-02-08 17:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 3:42 linux-next: build failure after merge of the slab tree Stephen Rothwell
2011-01-31 19:32 ` Pekka Enberg
2011-02-03 15:19 ` Christoph Lameter
2011-02-08 15:53 ` Christoph Lameter
2011-02-08 15:55 ` Christoph Lameter
2011-02-08 16:50 ` Ted Ts'o
2011-02-08 17:11 ` Sedat Dilek
2011-02-08 17:44 ` Christoph Lameter [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-01 5:28 Stephen Rothwell
2024-05-01 15:31 ` Vlastimil Babka
2022-11-25 1:49 Stephen Rothwell
2022-11-25 7:50 ` Vlastimil Babka
2022-11-24 4:39 Stephen Rothwell
2022-11-24 8:56 ` Vlastimil Babka
2022-09-06 6:51 Stephen Rothwell
2022-09-06 7:53 ` Vlastimil Babka
2022-09-06 18:37 ` Alexei Starovoitov
2022-09-07 3:05 ` Alexei Starovoitov
2022-09-07 6:40 ` Vlastimil Babka
2022-09-07 7:45 ` Stephen Rothwell
2013-07-10 2:56 Stephen Rothwell
2013-07-10 7:00 ` Pekka Enberg
2013-07-10 18:48 ` Christoph Lameter
2013-07-11 6:42 ` Pekka Enberg
2010-12-09 3:03 Stephen Rothwell
2010-12-09 16:25 ` Pekka Enberg
2010-10-27 0:33 Stephen Rothwell
2010-10-27 7:29 ` Pekka Enberg
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=alpine.DEB.2.00.1102081144170.15931@router.home \
--to=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=sandeen@redhat.com \
--cc=sedat.dilek@googlemail.com \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).