All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: [GIT PULL FOR v4.5] Davinci staging fixes
Date: Tue, 17 Nov 2015 15:44:11 -0200	[thread overview]
Message-ID: <20151117154411.7888779b@recife.lan> (raw)
In-Reply-To: <CA+V-a8t1RWFg-BvZvPG+zAH1yc531SEOPOh79KY5_JunHRsc4g@mail.gmail.com>

Em Tue, 17 Nov 2015 17:14:10 +0000
"Lad, Prabhakar" <prabhakar.csengg@gmail.com> escreveu:

> Hi Mauro,
> 
> On Tue, Nov 17, 2015 at 4:29 PM, Mauro Carvalho Chehab
> <mchehab@osg.samsung.com> wrote:
> > Em Mon, 09 Nov 2015 23:27:02 +0200
> > Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:
> >
> >> Hi Mauro,
> >>
> >> I've collected the pending Davinci staging fixes from patchwork and prepared a
> >> branch for you.
> >>
> >> Prabhakar, is that fine with you ? Do you still maintain the driver ? If so,
> >> do you expect patches to be picked up when you ack them, or can you collect
> >> them in a branch somewhere and send a pull request ?
> >
> > As the patches on this tree are trivial, and one of them has Prabhakar's ack,
> > I'll apply them, as I'm assuming that they're all ok for Prabhakar.
> >
> Somehow this mail got buried into my inbox, If Laurent can pick it that’s fine
> with me Or else Ill create a pull request for you.

Laurent picked and I applied them from his tree ;)

Regards,
Mauro

      reply	other threads:[~2015-11-17 17:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 21:27 [GIT PULL FOR v4.5] Davinci staging fixes Laurent Pinchart
2015-11-17 16:29 ` Mauro Carvalho Chehab
2015-11-17 17:14   ` Lad, Prabhakar
2015-11-17 17:44     ` Mauro Carvalho Chehab [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=20151117154411.7888779b@recife.lan \
    --to=mchehab@osg.samsung.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=prabhakar.csengg@gmail.com \
    /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.