From: Pierre Ossman <drzeus@drzeus.cx>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, sshtylyov@ru.mvista.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/8] Alchemy: register mmc platform device for db1200/pb1200 boards.
Date: Fri, 20 Jun 2008 17:46:07 +0200 [thread overview]
Message-ID: <20080620174607.50ad6874@mjolnir.drzeus.cx> (raw)
In-Reply-To: <20080612135810.GA25352@roarinelk.homelinux.net>
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
On Thu, 12 Jun 2008 15:58:10 +0200
Manuel Lauss <mano@roarinelk.homelinux.net> wrote:
> On Thu, Jun 12, 2008 at 02:47:30PM +0100, Ralf Baechle wrote:
> > On Thu, Jun 12, 2008 at 03:42:48PM +0200, Pierre Ossman wrote:
> >
> > >
> > > How's the dependency issue though? Will this series be bisectable in my
> > > tree?
> >
> > If we're only talking about a build, there should be no dependencies
> > between the Alchemy and the MMC parts of the series. The Alchemy part
> > sorts the device registration and that's a separate construction site
> > from the rest. Of course with only one applied things won't work
> > terribly well but that would only be temporarily.
>
> FWIW, I build tested-tested the DB1200 defconfig after each patch applied.
> As Ralf said, patch 1 alone isn't terribly useful on it, but it should work.
>
This patch does not apply against HEAD. Are you sure there aren't any
dependencies on what Ralf has in his tree? If so, perhaps this should
be in the MIPS tree.
Rgds
--
-- Pierre Ossman
WARNING: This correspondence is being monitored by the
Swedish government. Use end-to-end encryption where
possible.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-06-20 15:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 6:35 [PATCH 0/8] au1xmmc updates #4 Manuel Lauss
2008-06-09 6:36 ` [PATCH 1/8] au1xmmc: remove db1200 board code, rewrite probe Manuel Lauss
2008-06-09 6:37 ` [PATCH 2/8] Alchemy: register mmc platform device for db1200/pb1200 boards Manuel Lauss
2008-06-12 9:02 ` Ralf Baechle
2008-06-12 10:18 ` Ralf Baechle
2008-06-12 12:18 ` Manuel Lauss
2008-06-12 12:26 ` Ralf Baechle
2008-06-12 13:42 ` Pierre Ossman
2008-06-12 13:47 ` Ralf Baechle
2008-06-12 13:53 ` Pierre Ossman
2008-06-12 13:58 ` Manuel Lauss
2008-06-20 15:46 ` Pierre Ossman [this message]
2008-06-20 16:12 ` Manuel Lauss
2008-06-20 17:03 ` Pierre Ossman
2008-06-20 17:13 ` Manuel Lauss
2008-06-20 17:43 ` Pierre Ossman
2008-06-09 6:37 ` [PATCH 3/8] au1xmmc: enable 4 bit transfer mode Manuel Lauss
2008-06-09 6:38 ` [PATCH 4/8] au1xmmc: SDIO IRQ support Manuel Lauss
2008-06-09 6:38 ` [PATCH 5/8] au1xmmc: codingstyle tidying Manuel Lauss
2008-06-09 6:39 ` [PATCH 6/8] au1xmmc: abort requests early if no card is present Manuel Lauss
2008-06-09 6:39 ` [PATCH 7/8] Alchemy: remove unused MMC macros from db1x00 header Manuel Lauss
2008-06-12 10:21 ` Ralf Baechle
2008-06-09 6:40 ` [PATCH 8/8] au1xmmc: new maintainer Manuel Lauss
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=20080620174607.50ad6874@mjolnir.drzeus.cx \
--to=drzeus@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mano@roarinelk.homelinux.net \
--cc=ralf@linux-mips.org \
--cc=sshtylyov@ru.mvista.com \
/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
all inboxes | Powered by JetHome®