public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: sroas@roath.org (Stefan Roas)
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.25.10
Date: Sat, 5 Jul 2008 00:18:48 +0200	[thread overview]
Message-ID: <20080704221847.GA3761@master.roath.intern> (raw)
In-Reply-To: <555236.75770.qm@web52912.mail.re2.yahoo.com>

On Thu Jul 03, 2008 at 16:42:01, Chris Rankin wrote:
> > Again, if the above information is somehow insufficient as to what
> > exactly is fixed in the -stable releases, and anyone has questions about
> > how these release announcements are created, please let me know.
> 
> Well, for example:
> 
> I have only machines with 32 bit CPUS, none of them is hot-pluggable and none has an i915 graphics chip. All my local users are "trusted", nor am I running any multi-threaded Java applications on SMP systems. (I also have no idea what ICM pages are, but they sound jolly impressive!)
> 
> And what is "native_read_tscp" all about?

To some degree I can understand that you are not sure of whether you are
affected or not. On the other hand you should probably be, when running
your own kernels on a productive system. After all there seems to be a
general agreement that distribution vendors take care of the stabilization
and bug fixing of their particular kernels. As far as I am
concerned, I'm grateful that there are these stable releases at all and I very
much consider it additional work for everyone in the release team. To that
end it should be your task to check whether the update affects you or not.

After all the releases are publicly announced on probably the busiest
mailing list on earth. That offers anyone the chance to add additional
information to the releases (there has been a discussion recently about
security implications that weren't mentioned in the announcement. Just
replying to the announcement will add the needed information, and as the
discussion showed, people actually do add information).

To sum all the above up: IMHO the announcements are great, the work of the
stable team is great and I wouldn't really want to push more work on the
people that voluntarily spend their time on this branch by explaining every
detail of every patch.

Just my 2 cents.

Best regards,
  Stefan

  parent reply	other threads:[~2008-07-04 22:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 23:42 Linux 2.6.25.10 Chris Rankin
2008-07-03 23:51 ` Greg KH
2008-07-04 17:32 ` Nix
2008-07-04 22:18 ` Stefan Roas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-03  3:58 Greg KH
2008-07-03  3:58 ` Greg KH
2008-07-03 17:08 ` Bart Van Assche
2008-07-03 17:29   ` Greg KH
2008-07-03 18:57     ` Greg KH
2008-07-03 19:31       ` pageexec
2008-07-05  7:54     ` Bart Van Assche
2008-07-08  4:12       ` Greg KH

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=20080704221847.GA3761@master.roath.intern \
    --to=sroas@roath.org \
    --cc=linux-kernel@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