All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Kieran Bingham <kieran@ksquared.org.uk>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PULL REQUEST] VSP1 Image Partitioning algorithm
Date: Mon, 19 Sep 2016 17:57:24 +0200	[thread overview]
Message-ID: <CAMuHMdXFbbzH1Zzzxu68CwLtrccSbtyDrLJGpof2nq7-6CwGtQ@mail.gmail.com> (raw)
In-Reply-To: <1473871510-13807-1-git-send-email-kieran@bingham.xyz>

Hi Kieran,

On Wed, Sep 14, 2016 at 6:45 PM, Kieran Bingham <kieran@ksquared.org.uk> wrote:
> Please consider integrating the latest VSP1 next branch to provide the
> image partitioning algorithm into renesas-drivers
>
> Regards
>
> Kieran
>
>
> The following changes since commit c3b809834db8b1a8891c7ff873a216eac119628d:
>
>   [media] pulse8-cec: fix compiler warning (2016-09-12 06:42:44 -0300)
>
> are available in the git repository at:
>
>   git://linuxtv.org/pinchartl/media.git vsp1/next
>
> for you to fetch changes up to 9f39e31fbb3fb6ebd75d7012d3574def2f5da596:
>
>   v4l: vsp1: Fix spinlock in mixed IRQ context function (2016-09-14 13:06:51 +0300)

In the mean time, this has been rebased, and more commits have been added?
I will only pull tomorrow anyway...

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:[~2016-09-19 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 16:45 [PULL REQUEST] VSP1 Image Partitioning algorithm Kieran Bingham
2016-09-19 15:57 ` Geert Uytterhoeven [this message]
2016-09-19 17:17   ` Kieran Bingham

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=CAMuHMdXFbbzH1Zzzxu68CwLtrccSbtyDrLJGpof2nq7-6CwGtQ@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=kieran@ksquared.org.uk \
    --cc=linux-renesas-soc@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 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.