From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Dave Airlie <airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PULL] drm-tegra-fixes
Date: Thu, 20 Jun 2013 23:07:11 +0200 [thread overview]
Message-ID: <20130620210710.GA9707@mithrandir> (raw)
In-Reply-To: <CAPM=9tz_-m+kZo9+BJ1P-3-d01+HDEQkM0-Kvdc4GFVffex5gg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
On Fri, Jun 21, 2013 at 06:37:30AM +1000, Dave Airlie wrote:
> > git://anongit.freedesktop.org/tegra/linux.git drm/fixes
> >
> > for you to fetch changes up to 2b15aa0fd466a4b2defdfd84c0b5168804b3eb33:
> >
> > gpu: host1x: Rework CPU syncpoint increment (2013-06-20 12:21:38 +0200)
> >
> > I know this comes awfully late and is much bigger than I'd like. It's
> > all my fault, though, since I've been travelling a lot lately and just
> > didn't find the time to prepare this earlier. I did want to sort out
> > patches that didn't warrant to go in before the final 3.10 release, but
> > all met the criteria as far as I could tell.
> >
>
> Don't think I want to submit this to Linus, its way too much at this point,
>
> User visible oops or regressions is all you get now really.
Okay, I understand. Can you take this pull request for 3.11 instead?
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-20 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 10:36 [PULL] drm-tegra-fixes Thierry Reding
2013-06-20 20:37 ` Dave Airlie
[not found] ` <CAPM=9tz_-m+kZo9+BJ1P-3-d01+HDEQkM0-Kvdc4GFVffex5gg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-20 21:07 ` Thierry Reding [this message]
2013-06-22 11:07 ` Thierry Reding
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=20130620210710.GA9707@mithrandir \
--to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).