From: Pierre Ossman <drzeus-list@drzeus•cx>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
"Michał Mirosław" <mirq-linux@rere•qmqm.pl>
Subject: Re: linux-next: mmc tree build failure
Date: Thu, 4 Jun 2009 07:39:19 +0200 [thread overview]
Message-ID: <20090604073919.6422358d@mjolnir.ossman.eu> (raw)
In-Reply-To: <20090604120435.bc32b890.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
On Thu, 4 Jun 2009 12:04:35 +1000
Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Hi Pierre,
>
> Today's linux-next build (powerpc_ppc64_defconfig) failed like this:
>
> drivers/misc/Kconfig:238: can't open file "drivers/misc/cb710/Kconfig"
>
> Caused by commit f8d1918a2e7adbfdde0efc1a9a22cca3d5c5cae9 ("mmc: Driver
> for CB710/720 memory card reader (MMC part)").
>
> I have used the version of the mmc tree from next-20090603 for today.
>
> Please build test what you are submitting to linux-next.
Sorry, it seems I had some files in my working that weren't properly
added. :/
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
rdesktop, core developer http://www.rdesktop.org
TigerVNC, core developer http://www.tigervnc.org
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-06-04 5:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 2:04 linux-next: mmc tree build failure Stephen Rothwell
2009-06-04 5:39 ` Pierre Ossman [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-04 4:28 Stephen Rothwell
2008-12-04 4:54 ` Philip Langdale
2008-12-09 3:42 ` Stephen Rothwell
2008-12-09 6:47 ` Pierre Ossman
2008-12-09 7:16 ` 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=20090604073919.6422358d@mjolnir.ossman.eu \
--to=drzeus-list@drzeus$(echo .)cx \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mirq-linux@rere$(echo .)qmqm.pl \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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