public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
	Pavel Machek <pavel@suse.cz>, Josh Boyer <jwboyer@gmail.com>,
	Greg KH <greg@kroah.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Adrian Bunk is now taking over the 2.6.16-stable branch
Date: Sat, 12 Aug 2006 18:24:47 +0200	[thread overview]
Message-ID: <20060812162447.GE5084@stusta.de> (raw)
In-Reply-To: <44DB1F19.8000504@s5r6.in-berlin.de>

On Thu, Aug 10, 2006 at 01:57:13PM +0200, Stefan Richter wrote:
> Adrian Bunk wrote:
> ...
> > I'm currently 
> > going through all 2.6.17.7 and 2.6.17.8 patches looking for patches I 
> > should apply.
> 
> Suggested updates for drivers/ieee1394/:
> 
> (from 2.6.17.2)
>   Fix broken suspend/resume in ohci1394
> should be applicable as-is. This does not add full suspend/resume
> functionality to ohci1394 but it fixes fatal side effects on other
> on-board hardware after resume.
> 
> (from 2.6.17.8)
>   ieee1394: sbp2: enable auto spin-up for Maxtor disks
> doesn't apply to 2.6.16 as-is.
> https://bugzilla.novell.com/show_bug.cgi?id=183011#c6 has an adapted
> version. I will mail it to you with proper description and signed-off-by
> later today. While I am at it, I will resend that ohci1394 patch too.

Thanks, I've applied them both.

> I have a related question about your plans with Linux 2.6.16.yy.
> Documentation/stable_kernel_rules.txt says:
> 
>  - It must fix a problem that causes a build error (but not for things
>    marked CONFIG_BROKEN), an oops, a hang, data corruption, a real
>    security issue, or some "oh, that's not good" issue.  In short,
>    something critical.
> 
> I plan to submit a patch of the kind "fix recognition of a quirky
> device" for 2.6.18. That patch does not fix an oops, hang, data
> corruption, or security hole. (The patch will fulfill all other criteria
> from stable_kernel_rules.) Do you consider "can't use that shiny device
> under Linux" as "oh, that's not good" in the context of Linux 2.6.16.yy?
>...

If the device doesn't work, it's an "oh, that's not good" issue. ;-)

More seriously:

I consider stable_kernel_rules.txt as a more formal description of
"avoid regressions".

If the patch is tested, unlikely to break anything and included in 
Linus' tree it's a candidate for 2.6.16.

> Stefan Richter

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2006-08-12 16:24 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-09 21:45 Adrian Bunk is now taking over the 2.6.16-stable branch Chuck Ebbert
2006-08-09 22:00 ` Adrian Bunk
2006-08-09 22:18   ` Greg KH
2006-08-09 22:45     ` Adrian Bunk
2006-08-09 22:53       ` Greg KH
2006-08-09 23:05         ` Chris Wright
2006-08-09 23:20     ` Rene Scharfe
2006-08-10 11:57   ` Stefan Richter
2006-08-10 16:43     ` [PATCH 2.6.16.27] Fix broken suspend/resume in ohci1394 Stefan Richter
2006-08-10 16:45     ` [PATCH 2.6.16.27] ieee1394: sbp2: enable auto spin-up for Maxtor disks Stefan Richter
2006-08-12 16:24     ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-03 20:49 Adrian Bunk is now taking over the 2.6.16-stable branch Greg KH
2006-08-04  2:43 ` Josh Boyer
2006-08-04  6:26   ` Jan Engelhardt
2006-08-04 23:00   ` Adrian Bunk
2006-08-06  0:46     ` Andrea Arcangeli
2006-08-06  4:52       ` Greg KH
2006-08-20 22:30         ` Andrea Arcangeli
2006-08-20 23:05           ` Alan Cox
2006-08-20 23:17             ` Andrea Arcangeli
2006-08-21  6:21             ` David Miller
2006-08-21  9:35               ` Andrea Arcangeli
2006-08-22  7:27                 ` Matthias Andree
2006-08-24 13:00                 ` Pavel Machek
     [not found]           ` <20060820185123.e84fafaf.seanlkml@sympatico.ca>
2006-08-20 22:51             ` Sean
2006-08-20 23:15             ` Andrea Arcangeli
2006-08-20 23:38               ` Adrian Bunk
2006-08-21  0:05               ` Willy Tarreau
2006-08-21 13:33                 ` Andrea Arcangeli
2006-08-06  6:17     ` Willy Tarreau
2006-08-07 12:40     ` Pavel Machek
2006-08-07 17:59       ` Adrian Bunk
2006-08-07 23:30         ` Pavel Machek
2006-08-08 19:55           ` Adrian Bunk

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=20060812162447.GE5084@stusta.de \
    --to=bunk@stusta.de \
    --cc=76306.1226@compuserve.com \
    --cc=greg@kroah.com \
    --cc=jwboyer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=stefanr@s5r6.in-berlin.de \
    /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