public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Greg KH <greg@kroah.com>, Neil Brown <neilb@cse.unsw.edu.au>,
	linux-kernel@vger.kernel.org, Chris Wright <chrisw@osdl.org>,
	torvalds@osdl.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC] -stable, how it's going to work.
Date: Thu, 10 Mar 2005 09:43:59 -0800	[thread overview]
Message-ID: <20050310174359.GP5389@shell0.pdx.osdl.net> (raw)
In-Reply-To: <1110475644.12805.43.camel@mindpipe>

* Lee Revell (rlrevell@joe-job.com) wrote:
> On Thu, 2005-03-10 at 08:43 -0800, Greg KH wrote:
> > That, and a zillion other specific wordings that people suggested fall
> > under the:
> > 	or some "oh, that's not good" issue
> > rule.
> 
> So just to be 100% clear, no sound with 2.6.N where the sound worked
> with 2.6.N-1 absolutely does qualify.  Right?

Depends, is listening to music while you work critical...? j/k ;-)
Yeah, that's a driver regression...used to work, now it's broken.
If fix is back out all changes, that's not so nice, if it's a
'one-liner' then definitely.  Have a concrete example and patch?

thanks
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  parent reply	other threads:[~2005-03-10 17:56 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  7:28 [RFC] -stable, how it's going to work Greg KH
2005-03-09  9:56 ` Andi Kleen
2005-03-09 10:10   ` Arjan van de Ven
2005-03-09 10:17     ` Russell King
2005-03-09 10:24       ` Arjan van de Ven
2005-03-09 10:32         ` Russell King
2005-03-09 10:28       ` Andi Kleen
2005-03-09 14:20   ` Marcelo Tosatti
2005-03-09 18:00   ` Alan Cox
2005-03-09 18:29     ` Greg KH
2005-03-09 18:29     ` Chris Wright
2005-03-09 19:30     ` Andi Kleen
2005-03-09 18:28   ` Chris Wright
2005-03-09 19:44     ` Andi Kleen
2005-03-09 20:16       ` Chris Wright
2005-03-09 22:49       ` Russell King
2005-03-09 18:34   ` Greg KH
2005-03-09 19:39     ` Andi Kleen
2005-03-09 20:03       ` Greg KH
2005-03-09 20:25   ` Bill Davidsen
2005-03-10 10:00 ` Neil Brown
2005-03-10 10:17   ` Arjan van de Ven
2005-03-11  1:49     ` Neil Brown
2005-03-11  4:58       ` Chris Friesen
2005-03-11  7:07         ` Andi Kleen
2005-03-10 16:43   ` Greg KH
2005-03-10 17:27     ` Lee Revell
2005-03-10 17:31       ` Greg KH
2005-03-10 18:25         ` Lee Revell
2005-03-11 10:13           ` Pavel Machek
2005-03-10 17:43       ` Chris Wright [this message]
2005-03-10 17:51         ` Lee Revell
2005-03-10 17:44       ` Linus Torvalds
2005-03-11  0:10     ` Neil Brown
2005-03-11  2:43       ` J. Bruce Fields

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=20050310174359.GP5389@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=rlrevell@joe-job.com \
    --cc=torvalds@osdl.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