linux-kernel - Re: [PATCH v2 0/7] atmel-mci: updates for 2.6.28

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]

Message-ID: <20081012105021.46450333@mjolnir.drzeus.cx>
Date:	Sun, 12 Oct 2008 10:50:21 +0200
From:	Pierre Ossman <drzeus-list@...eus.cx>
To:	Haavard Skinnemoen <haavard.skinnemoen@...el.com>
Cc:	kernel@...32linux.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/7] atmel-mci: updates for 2.6.28

On Sun, 5 Oct 2008 20:46:17 +0200
Haavard Skinnemoen <haavard.skinnemoen@...el.com> wrote:

> 
> If you're happy with this patchset, could you please pull
> 

Fairly happy. There is the one thing to fix with the clock, but as no
cards implement power control yet, you can send that patch later.

There's also the open issue of bytes_xfered. Please send a patch for
that ASAP (provided it just isn't a misunderstanding on my part :)).

>   git://git.kernel.org/pub/scm/linux/kernel/git/hskinnemoen/atmel-mci-2.6.28.git master
> 
> instead of applying the patches? If you do that, I can pull it into my
> avr32 tree as well and fix up any conflicts. I won't do that before
> you've pulled it, of course, and it's probably best if no one base any
> further work on it until it's accepted because I might have to rebase
> it if someone finds any issues during review.

Pulled and will be sent to Linus just as soon as I have everything else
queued up.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.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.

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