All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: Dave Airlie <airlied@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	stable@vger.kernel.org,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/radeon/dpm: resume fixes for some systems
Date: Mon, 02 Jun 2014 10:10:09 +0200	[thread overview]
Message-ID: <538C3161.9070302@vodafone.de> (raw)
In-Reply-To: <CAPM=9tyr3mhDPea8AE=GpwTTmzM3=CBZrS2ps=Dse23B2xZb=Q@mail.gmail.com>

Am 02.06.2014 05:39, schrieb Dave Airlie:
>> I've just added this to my 3.15 queue, but it looks like Linus is going to
>> tag 3.15 tomorrow and Dave already send out his most likely last pull
>> request.
>>
>> Going to send out another pull request in the evening if I can get the VM
>> crashes resolved as well, but I doubt it will be included.
>>
> Since Linus is playing with the merge window overlap, I've taken this
> patch into my -fixes
> to send to him for the final one.

OK. In this case I'm preparing another -fixes pull request for you, got 
two or three more patches that probably need CC stable as well.

> Please try and get a radeon tree asap for -next.

Alex already prepared a drm-next-3.16-wip tree, but this one still needs 
a rebase and is also missing a couple of more things that I like to get 
into 3.16 as well.

Christian.

  reply	other threads:[~2014-06-02  8:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-30 16:40 [PATCH] drm/radeon/dpm: resume fixes for some systems Alex Deucher
2014-05-31  9:06 ` Christian König
2014-06-02  3:39   ` Dave Airlie
2014-06-02  8:10     ` Christian König [this message]
2014-06-02 15:14       ` Alex Deucher
2014-06-02 15:18         ` Christian König

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=538C3161.9070302@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=stable@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.