linux-kernel - Re: [PATCH 2/8] Alchemy: register mmc platform device for db1200/pb1200 boards.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 20 Jun 2008 17:46:07 +0200
From:	Pierre Ossman <drzeus@...eus.cx>
To:	Manuel Lauss <mano@...rinelk.homelinux.net>
Cc:	Ralf Baechle <ralf@...ux-mips.org>, linux-mips@...ux-mips.org,
	sshtylyov@...mvista.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/8] Alchemy: register mmc platform device for
 db1200/pb1200 boards.

On Thu, 12 Jun 2008 15:58:10 +0200
Manuel Lauss <mano@...rinelk.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.

Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)