stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: <stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [34-longterm 179/179] x86/PCI: do not tie MSI MS-7253 use_crs quirk to BIOS version
Date: Tue, 15 May 2012 12:03:50 -0400	[thread overview]
Message-ID: <20120515160350.GB17760@windriver.com> (raw)
In-Reply-To: <20120515154743.04879bde@pyramind.ukuu.org.uk>

[Re: [34-longterm 179/179] x86/PCI: do not tie MSI MS-7253 use_crs quirk to BIOS version] On 15/05/2012 (Tue 15:47) Alan Cox wrote:

> On Tue, 15 May 2012 15:44:55 +0100
> Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> 
> > O> MS-7253, for which we already have a quirk, but the short-sighted
> > > author tied the quirk to a single BIOS version, making it not kick in
> > 
> > It's our usual policy to tie to particular BIOS versions because these
> > things are often BIOS specific and come and go with updates.
> 
> Doh ignore that, the point is valid but not in a -longterm context

The prefix "34-longterm" isn't as clear as it was before we went to 3.0
so I'll change it to "2.6.34-stable" for next time.  We've stopped
separating longterm from stable on the server anyways.

Thanks,
Paul.


  parent reply	other threads:[~2012-05-15 16:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1337048075-6132-1-git-send-email-paul.gortmaker@windriver.com>
2012-05-15  3:01 ` [34-longterm 000/179] v2.6.34.12 longterm review Paul Gortmaker
     [not found] ` <1337048075-6132-168-git-send-email-paul.gortmaker@windriver.com>
     [not found]   ` <alpine.LSU.2.00.1205142126180.2196@eggly.anvils>
     [not found]     ` <1337079117.27694.28.camel@twins>
2012-05-15 16:02       ` [34-longterm 167/179] futex: Fix regression with read only mappings Paul Gortmaker
2012-05-15 18:55         ` Willy Tarreau
     [not found] ` <1337048075-6132-180-git-send-email-paul.gortmaker@windriver.com>
     [not found]   ` <20120515154455.39cfbad2@pyramind.ukuu.org.uk>
     [not found]     ` <20120515154743.04879bde@pyramind.ukuu.org.uk>
2012-05-15 16:03       ` Paul Gortmaker [this message]
     [not found] ` <1337048075-6132-75-git-send-email-paul.gortmaker@windriver.com>
     [not found]   ` <20120515050221.GA4292@burratino>
2012-05-15 16:33     ` [34-longterm 074/179] xen: Use IRQF_FORCE_RESUME Paul Gortmaker

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=20120515160350.GB17760@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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 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).