All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [GIT PULL FOR v3.20] tda998x enhancement
Date: Fri, 16 Jan 2015 18:37:57 +0200	[thread overview]
Message-ID: <2294726.tUKoJtsKHf@avalon> (raw)
In-Reply-To: <20150116162600.GM12302@n2100.arm.linux.org.uk>

Hi Russell,

On Friday 16 January 2015 16:26:00 Russell King - ARM Linux wrote:
> On Fri, Jan 16, 2015 at 06:17:39PM +0200, Laurent Pinchart wrote:
> > On Friday 16 January 2015 15:46:28 Russell King - ARM Linux wrote:
> >> On Fri, Jan 16, 2015 at 05:44:52PM +0200, Laurent Pinchart wrote:
> >>> Hi Dave,
> >>> 
> >>> The following changes since commit
> >>> adc31849b27fefeca6c225d3895143a2ec6970fa:
> >>>   Merge tag 'drm-intel-next-2014-12-19' of
> >>>   git://anongit.freedesktop.org/drm-
> >>> 
> >>> intel into drm-next (2015-01-10 08:46:24 +1000)
> >>> 
> >>> are available in the git repository at:
> >>>   git://linuxtv.org/pinchartl/fbdev.git drm/next/tda998x
> >> 
> >> Err... please send to me instead so I can merge them with the other
> >> patches I have queued.
> > 
> > I've sent you an e-mail a couple of weeks ago to ask whether you wanted to
> > take the patch in your tree (see
> > http://comments.gmane.org/gmane.comp.video.dri.devel/119214).
> 
> Yes, I found it, you sent it on the 23rd December.  Do you not think people
> would be busy around Christmas time, and possibly would not bother reading
> email?
> 
> Personally, I decided to stop on the weekend before Christmas, and only
> resume on the 5th Jan.  However, I was ill with the flu, and I'm still
> recovering from that three weeks on, so I didn't resume on the 5th -
> that meant a few hundred extra messages, and I ended up deciding just
> to ignore all that email (which included your message), rather than try
> to catch up.

If it wasn't clear from my previous mail, no blame meant at all.

> However, upon reading your email, and the original, you indicated that it
> depends on another patch which I have no visibility of:
>
> | This patch has been compile-tested only as I lack test hardware. It
> | depends on "[PATCH v4 6/9] drm: Decouple EDID parsing from I2C adapter"
> | previously posted to the dri-devel mailing list.
> 
> How can I merge your patch when you say that it depends on another patch
> which I have no access to?  What is the status of this patch?  Is it
> merged into mainline, or is it a patch in Dave's DRM tree?

The patch has been merged in v3.19-rc1 as 
18df89fef2d5c7cfd15ab898b17a292d00222b0c.

> > I'm certainly not in a good position to complain when mails slip through
> > the cracks ;-)
> > 
> > Could you please take this patch in your tree and push it for v3.20 ?
> 
> I'm not entirely thrilled by the thought of merging Dave's tree into mine.
> Would it be possible to base it on some -rc release please?  What about
> its dependent patch, which presumably this patch breaks without?

The patch applies on v3.19-rc1 without any issue. For your convenience I've 
just resent it with the Reviewed-by and Tested-by lines.

-- 
Regards,

Laurent Pinchart

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2015-01-16 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 15:44 [GIT PULL FOR v3.20] tda998x enhancement Laurent Pinchart
2015-01-16 15:46 ` Russell King - ARM Linux
2015-01-16 16:17   ` Laurent Pinchart
2015-01-16 16:26     ` Russell King - ARM Linux
2015-01-16 16:37       ` Laurent Pinchart [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=2294726.tUKoJtsKHf@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux@arm.linux.org.uk \
    /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.