All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PULL REQUEST] renesas/topic/sdhi-dma-sync-v3 for renesas drivers
Date: Thu, 16 Mar 2017 12:05:26 +0100	[thread overview]
Message-ID: <CAMuHMdXjjZgjRqmzQYtqTQGuMv6qWrG+GVeQK37mpNK2AU-eoQ@mail.gmail.com> (raw)
In-Reply-To: <20170316110013.kmjytn4jipo6sacj@ninjato>

Hi Wolfram,

On Thu, Mar 16, 2017 at 12:00 PM, Wolfram Sang <wsa@the-dreams.de> wrote:
> here is an updated topic branch (v3 instead of v2) for renesas-drivers,
> also rebased to current mmc/next. Please pull.
>
> Kind regards,
>
>    Wolfram
>
>
> The following changes since commit 05d1ea17f58de925e46d97b305d3cacbb84a0eb6:
>
>   Merge branch 'fixes' into next (2017-03-14 17:19:20 +0100)
>
> are available in the git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/topic/sdhi-dma-sync-v3
>
> for you to fetch changes up to 1309db3202ae35b0372f414dbc50ad6889027b5e:
>
>   mmc: tmio: always unmap DMA before waiting for interrupt (2017-03-16 11:37:58 +0100)

Looks fine, thanks!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      reply	other threads:[~2017-03-16 11:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 11:00 [PULL REQUEST] renesas/topic/sdhi-dma-sync-v3 for renesas drivers Wolfram Sang
2017-03-16 11:05 ` Geert Uytterhoeven [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=CAMuHMdXjjZgjRqmzQYtqTQGuMv6qWrG+GVeQK37mpNK2AU-eoQ@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.