mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: kernel@avr32linux.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/7] atmel-mci: updates for 2.6.28
Date: Sun, 12 Oct 2008 10:50:21 +0200	[thread overview]
Message-ID: <20081012105021.46450333@mjolnir.drzeus.cx> (raw)
In-Reply-To: <20081005204617.14868dc4@hskinnemo-gx745.norway.atmel.com>

[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]

On Sun, 5 Oct 2008 20:46:17 +0200
Haavard Skinnemoen <haavard.skinnemoen@atmel.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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2008-10-12  8:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-05 16:21 Haavard Skinnemoen
2008-10-05 16:21 ` [PATCH v2 1/7] atmel-mci: Implement tasklet as a state machine Haavard Skinnemoen
2008-10-05 16:21   ` [PATCH v2 2/7] atmel-mci: Don't stop the clock between transfers Haavard Skinnemoen
2008-10-05 16:21     ` [PATCH v2 3/7] atmel-mci: Platform code for supporting multiple mmc slots Haavard Skinnemoen
2008-10-05 16:21       ` [PATCH v2 4/7] atmel-mci: support " Haavard Skinnemoen
2008-10-05 16:21         ` [PATCH v2 5/7] atmel-mci: Add experimental DMA support Haavard Skinnemoen
2008-10-05 16:21           ` [PATCH v2 6/7] atmel-mci: Don't overwrite error bits when NOTBUSY is set Haavard Skinnemoen
2008-10-05 16:21             ` [PATCH v2 7/7] atmel-mci: Add missing flush_dcache_page() in PIO transfer code Haavard Skinnemoen
2008-10-12  8:44           ` [PATCH v2 5/7] atmel-mci: Add experimental DMA support Pierre Ossman
2008-10-12  8:39         ` [PATCH v2 4/7] atmel-mci: support multiple mmc slots Pierre Ossman
2008-10-12 13:13           ` Haavard Skinnemoen
2008-10-12 15:58             ` Pierre Ossman
2008-10-12 16:07               ` Haavard Skinnemoen
2008-10-05 18:46 ` [PATCH v2 0/7] atmel-mci: updates for 2.6.28 Haavard Skinnemoen
2008-10-12  8:50   ` Pierre Ossman [this message]

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=20081012105021.46450333@mjolnir.drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=haavard.skinnemoen@atmel.com \
    --cc=kernel@avr32linux.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

all inboxes | Powered by JetHome®