From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Kieran Bingham <kieran.bingham@ideasonboard.com>
Subject: Re: [GIT PULL FOR renesas-drivers] v4l: vsp1: writeback prototype
Date: Wed, 10 May 2017 10:20:32 +0200 [thread overview]
Message-ID: <CAMuHMdVyCSgGZ1QcKaXeq6kjJBZJ8P4L0vmzDePk-o2HQwerXA@mail.gmail.com> (raw)
In-Reply-To: <1494348424-18246-1-git-send-email-kieran.bingham+renesas@ideasonboard.com>
Hi Kieran,
On Tue, May 9, 2017 at 6:47 PM, Kieran Bingham
<kieran.bingham+renesas@ideasonboard.com> wrote:
> The following changes since commit 13e0988140374123bead1dd27c287354cb95108e:
>
> docs: complete bumping minimal GNU Make version to 3.81 (2017-05-06 18:49:09 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kbingham/rcar.git tags/submissions/vsp1/writeback/v3
>
> for you to fetch changes up to 5debeb08338b520f52577ca6cf9be815a54c07ea:
>
> v4l: vsp1: Provide a writeback video device (2017-05-08 15:06:58 +0100)
Looks good, and merges cleanly into today's linux-next.
> v3:
> - Rebased to v4.12-rc1
Interesting... Where can I find v4.12-rc1? ;-)
I see this is based on an arbitrary commit in Linus' tree instead?
While that's OK for renesas-drivers, you never want to do this for a
pull request you
sent to an upstream maintainer.
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
next prev parent reply other threads:[~2017-05-10 8:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 16:47 [GIT PULL FOR renesas-drivers] v4l: vsp1: writeback prototype Kieran Bingham
2017-05-10 8:20 ` Geert Uytterhoeven [this message]
2017-05-10 8:27 ` Kieran Bingham
2017-05-10 8:29 ` Geert Uytterhoeven
2017-06-27 18:53 ` Geert Uytterhoeven
2017-06-28 8:07 ` 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=CAMuHMdVyCSgGZ1QcKaXeq6kjJBZJ8P4L0vmzDePk-o2HQwerXA@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).