All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org,
	stable-review@kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, mgalbraith@suse.de,
	tglx@linutronix.de
Subject: Re: [000/474] 2.6.33.8-longterm review
Date: Fri, 18 Mar 2011 10:21:54 +0100	[thread overview]
Message-ID: <AANLkTikmuQ6bCn9wws9Z83gZXRz2gRRsWd+8Q34DqaFL@mail.gmail.com> (raw)
In-Reply-To: <20110317213822.GA27980@kroah.com>

On Thu, Mar 17, 2011 at 10:38 PM, Greg KH <gregkh@suse.de> wrote:
> Yeah, I know what you are thinking, "What, 2.6.33, are you crazy?"
>
> I'd prefer it if you didn't answer that question...
>
> Anyway, yes, a .33 kernel release, strange isn't it.
>
> Turns out there are a lot of people "stuck" on the 2.6.33 kernel series
> for a variety of valid reasons, not the least being the Real Time
> patchset.  So, in the copious spare time I have, I've been trying to
> keep up with the patches that have been applied to the different
> longterm and stable kernel trees and have been queueing them up for .33
> as well.
>
> Here's the result of that.  A 474 patch series that is bigger than most
> people ever want to review, or see in their inboxes.  Because of that,
> it is ONLY being sent to the stable-review@kernel.org mailing list.  If
> you want to see the individual patches, look at the git tree of the
> patch queue, or look at that mailing list.
>
> So, if you are using .33, please give this patch a test and let me know
> if I've messed up anything (hint, I think I did, it's up to you to
> figure it out, consider it a test to see if anyone actually cares about
> this kernel version.)
>
> If I missed anything that I should have in here, please let me know.
>
> Responses should be made by Saturday, March 19, 2011, 21:00:00 UTC.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
>        kernel.org/pub/linux/kernel/v2.6/longterm-review/patch-2.6.33.8-rc1.gz
> and the diffstat can be found below.
>

There is no rc1, so I assume
http://kernel.org/pub/linux/kernel/v2.6/longterm-review/patch-2.6.33.8.bz2
is correct?
Which git tree do I want to use?

Thanks
John Kacur

  parent reply	other threads:[~2011-03-18  9:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 21:38 [000/474] 2.6.33.8-longterm review Greg KH
2011-03-17 21:22 ` [072/474] mm, x86: Saving vmcore with non-lazy freeing of vmas Greg KH
2011-03-17 21:22 ` [078/474] x86, kdump: Change copy_oldmem_page() to use cached addressing Greg KH
2011-03-17 21:24 ` [213/474] x86, hotplug: Use mwait to offline a processor, fix the legacy case Greg KH
2011-03-17 21:27 ` [421/474] powerpc/kexec: Fix orphaned offline CPUs across kexec Greg KH
2011-03-17 21:28 ` [430/474] MIPS: MTX-1: Make au1000_eth probe all PHY addresses Greg KH
2011-03-18  5:26 ` [000/474] 2.6.33.8-longterm review Mike Galbraith
2011-03-18  8:44 ` Thomas Gleixner
2011-03-19 14:47   ` Remy Bohmer
2011-03-20 12:52     ` Thomas Gleixner
2011-03-20 14:06       ` Niccolò Belli
2011-03-18  9:21 ` John Kacur [this message]
2011-03-18 19:36   ` Greg KH
2011-03-19 10:08     ` [stable] " John Kacur
     [not found] ` <20110317212903.394948496@clark.kroah.org>
2011-08-28 18:40   ` [regression] Re: [213/474] x86, hotplug: Use mwait to offline a processor, fix the legacy case Jonathan Nieder
     [not found]   ` <20110828184004.GA7690@elie.gateway.2wire.net>
2011-08-30 22:34     ` [stable] " 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=AANLkTikmuQ6bCn9wws9Z83gZXRz2gRRsWd+8Q34DqaFL@mail.gmail.com \
    --to=jkacur@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgalbraith@suse.de \
    --cc=stable-review@kernel.org \
    --cc=stable@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 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.