All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Herrmann <dh.herrmann@gmail.com>
To: sean darcy <seandarcy2@gmail.com>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [pull] radeon drm-fixes-3.17
Date: Mon, 1 Sep 2014 16:21:20 +0200	[thread overview]
Message-ID: <CANq1E4R2WsjvKpLcsTM0w3qyFV61f1AVM0MCi5UWKyFF5h1Tyg@mail.gmail.com> (raw)
In-Reply-To: <lu1sb2$nin$1@ger.gmane.org>

Hi

On Mon, Sep 1, 2014 at 3:29 PM, sean darcy <seandarcy2@gmail.com> wrote:
> On 08/22/2014 10:52 AM, Alex Deucher wrote:
>>
>> Hi Dave,
>>
>> This pull just contains some new pci ids.
>>
>> The following changes since commit
>> 20a984c2a51d379bce08ee1031b32020f273e532:
>>
>>    Merge tag 'drm-intel-fixes-2014-08-21' of
>> git://anongit.freedesktop.org/drm-intel (2014-08-22 07:29:52 +1000)
>>
>> are available in the git repository at:
>>
>>
>>    git://people.freedesktop.org/~agd5f/linux drm-fixes-3.17
>>
>> for you to fetch changes up to 37dbeab788a8f23fd946c0be083e5484d6f929a1:
>>
>>    drm/radeon: add additional SI pci ids (2014-08-22 10:47:59 -0400)
>>
>> ----------------------------------------------------------------
>> Alex Deucher (3):
>>        drm/radeon: add new KV pci id
>>        drm/radeon: add new bonaire pci ids
>>        drm/radeon: add additional SI pci ids
>>
>>   drivers/gpu/drm/radeon/cik.c | 1 +
>>   include/drm/drm_pciids.h     | 7 +++++++
>>   2 files changed, 8 insertions(+)
>>
>
> Is there any reason this pull can't go into fixes-3.16? or even 3.15? 3.17
> is months away for me! Fedora 20 is on 3.15.

This is not how kernel stable releases work. Fixes first go into the
current development branch and then are picked for older stable
kernels. This guarantees all fixes in older kernels are _always_ also
available in the development branch. So you just need to be patient
and it will be backported in a timely manner. (obviously only for
commits that are marked for stable, which should be the case for new
device IDs if they work fine on older kernels).

Thanks
David

  reply	other threads:[~2014-09-01 14:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 14:52 [pull] radeon drm-fixes-3.17 Alex Deucher
2014-09-01 13:29 ` sean darcy
2014-09-01 14:21   ` David Herrmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-09-24 20:45 Alex Deucher
2014-09-19  2:17 Alex Deucher
2014-09-18 23:30 Alex Deucher
2014-09-10 15:47 Alex Deucher
2014-08-27 22:26 Alex Deucher
2014-08-20 20:38 Alex Deucher
2014-08-15  5:32 Alex Deucher

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=CANq1E4R2WsjvKpLcsTM0w3qyFV61f1AVM0MCi5UWKyFF5h1Tyg@mail.gmail.com \
    --to=dh.herrmann@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=seandarcy2@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.