LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
Cc: Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: current git breaks resume
Date: Sun, 11 Feb 2007 18:56:19 +0100	[thread overview]
Message-ID: <20070211175619.GB3999@kernel.dk> (raw)
In-Reply-To: <20070211173624.GU6458@kernel.dk>

On Sun, Feb 11 2007, Jens Axboe wrote:
> On Sun, Feb 11 2007, Alexey Starikovskiy wrote:
> > Jens Axboe wrote:
> > >On Sun, Feb 11 2007, Len Brown wrote:
> > >  
> > >>On Friday 09 February 2007 14:03, Jens Axboe wrote:
> > >>    
> > >>>Hi,
> > >>>
> > >>>Unfortunately I'm a little short on time as I'll be travelling tomorrow,
> > >>>but of course preparing a new kernel for the laptop is something you
> > >>>want to do right before leaving. So I discovered that the current (well
> > >>>as of yesterday, HEAD is 5986a2ec35836a878350c54af4bd91b1de6abc59)
> > >>>doesn't resume on my x60. 2.6.20 works fine, so something broke since
> > >>>then.
> > >>>      
> > >>resume from RAM, or resume from disk?
> > >>    
> > >
> > >Resume from RAM, I never use suspend-to-disk.
> > >
> > >  
> > Jens,
> > Could you please test the patch I've sent?
> 
> Just saw it, will do.

With that patch applied, current git works as expected. Thanks!

-- 
Jens Axboe


      reply	other threads:[~2007-02-11 17:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 19:03 Jens Axboe
2007-02-10  9:49 ` Rafael J. Wysocki
2007-02-10 11:24   ` Jens Axboe
2007-02-10 11:50     ` Jens Axboe
2007-02-10 11:57       ` Rafael J. Wysocki
2007-02-11  3:28         ` Jens Axboe
2007-02-11  5:02 ` Len Brown
2007-02-11 14:34   ` Alexey Starikovskiy
2007-02-11 16:53   ` Jens Axboe
2007-02-11 17:31     ` Alexey Starikovskiy
2007-02-11 17:36       ` Jens Axboe
2007-02-11 17:56         ` Jens Axboe [this message]

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=20070211175619.GB3999@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=alexey.y.starikovskiy@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: current git breaks resume' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).