On Wed, Apr 10, 2013 at 08:20:14PM +0300, Gleb Natapov wrote:
> On Wed, Apr 10, 2013 at 09:39:57AM -0700, Greg KH wrote:
> > On Wed, Apr 10, 2013 at 01:57:51PM +0300, Gleb Natapov wrote:
> > > From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
> > >
> > > This fixes boot lockups with "no-kvmclock", when the host is not
> > > exposing this particular feature (QEMU: -cpu ...,-kvmclock) or when
> > > the kvmclock initialization failed for whatever reason.
> > >
> > > Reviewed-by: Marcelo Tosatti <mtosatti@xxxxxxxxxx>
> > > Signed-off-by: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
> > > Signed-off-by: Gleb Natapov <gleb@xxxxxxxxxx>
> > > ---
> > > arch/x86/kernel/kvmclock.c | 9 ++++++++-
> > > 1 file changed, 8 insertions(+), 1 deletion(-)
> >
> > <formletter>
> >
> > This is not the correct way to submit patches for inclusion in the
> > stable kernel tree. Please read Documentation/stable_kernel_rules.txt
> > for how to do this properly.
> >
> > </formletter>
> So the thing that is missing is upstream id? The patch is not in
> Linus tree yet, it waits for 3.10 merge window in kvm tree.
Which means it should have a 'cc: stable' in the commit message. Or,
if it is too late to add that, you'll have to send a request once
it's in Linus's tree.
> Will 3.8
> stable be still open for commits after 3.9 is released? If not it will
> unfortunately stay broken.
Greg has previously said that 3.8 is *not* a longterm branch, so it
will not be open for long after 3.9 is released.
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html