From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
apw@shadowen.org
Subject: Re: [Build Failure] 2.6.25-rc5-mm1 Build fails with allmodconfig probe_4drives undefined
Date: Tue, 11 Mar 2008 20:35:24 +0100 [thread overview]
Message-ID: <200803112035.24811.bzolnier@gmail.com> (raw)
In-Reply-To: <20080311104137.3c6b3f22.akpm@linux-foundation.org>
On Tuesday 11 March 2008, Andrew Morton wrote:
> On Tue, 11 Mar 2008 18:25:02 +0530
> Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
>
> > The 2.6.25-rc5-mm1 kernel build fails with allmodconfig
> >
> > MODPOST 2279 modules
> > ERROR: "probe_4drives" [drivers/ide/ide-core.ko] undefined!
>
> Yes, it has been doing this for a while. But apparently it doesn't happen
> for Bart with just his patch queue. <slightlypeeved>If your subssytem
> fails in my tree, that doesn't automatically make it my
> problem</slightlypeeved>
No need to peeve - it is not like I forget about the problem or ignored it
after I got your _first_ mail.
I just couldn't reproduce it here so instead I has been working on making
_all_ probe_* variables static (it should make the problem vanish alongside
some other nice improvements).
Thanks,
Bart
next prev parent reply other threads:[~2008-03-11 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080311011434.ad8c8d7d.akpm@linux-foundation.org>
2008-03-11 12:55 ` [Build Failure] 2.6.25-rc5-mm1 Build fails with allmodconfig probe_4drives undefined Kamalesh Babulal
2008-03-11 17:41 ` Andrew Morton
2008-03-11 19:35 ` Bartlomiej Zolnierkiewicz [this message]
2008-03-11 18:19 ` Andrew Morton
2008-03-11 19:36 ` Bartlomiej Zolnierkiewicz
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=200803112035.24811.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).