public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Jens Axboe <axboe@suse.de>
Cc: Chris Wright <chrisw@sous-sol.org>,
	torvalds@osdl.org, "Theodore Ts'o" <tytso@mit.edu>,
	Zwane Mwaikambo <zwane@arm.linux.org.uk>,
	Jeff Garzik <jeff@garzik.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Justin Forbes <jmforbes@linuxtx.org>,
	linux-kernel@vger.kernel.org,
	Chris Wedgewood <reviews@ml.cw.f00f.org>,
	Randy Dunlap <rdunlap@xenotime.net>, Mark Lord <liml@rtr.ca>,
	Dave Jones <davej@redhat.com>,
	Chuck Wolber <chuckw@quantumlinux.com>,
	stable@kernel.org, alan@lxorguk.ukuu.org.uk,
	Marcel Holtmann <marcel@holtmann.org>
Subject: Re: [stable] Re: [PATCH 07/11] the latest consensus libata resume fix
Date: Fri, 2 Jun 2006 13:02:44 -0700	[thread overview]
Message-ID: <20060602200244.GS18769@moss.sous-sol.org> (raw)
In-Reply-To: <20060602195046.GO4400@suse.de>

* Jens Axboe (axboe@suse.de) wrote:
> I'm not against the patch as such, but last I checked 2.6.16 actually
> worked ok. The timer fixes in 2.6.17-rc is what apparently got the
> resume breaking.
> 
> So unless there's a bug report on 2.6.16.x for this, then it's a little
> against the -stable rules to add it.

We did get a report that this fix was needed, but I'm not 100% which
kernel base the report was against.  Marcel, were you testing on a 2.6.16
base, or 2.6.17-rc?

thanks,
-chris

  parent reply	other threads:[~2006-06-02 20:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-02 19:46 [PATCH 00/11] -stable review Chris Wright
2006-06-02  7:00 ` [PATCH 01/11] Altix: correct ioc4 port order Chris Wright
2006-06-02  7:00 ` [PATCH 02/11] Altix: correct ioc3 " Chris Wright
2006-06-02  7:00 ` [PATCH 03/11] Cpuset: might sleep checking zones allowed fix Chris Wright
2006-06-02  7:00 ` [PATCH 04/11] PowerMac: force only suspend-to-disk to be valid Chris Wright
2006-06-02  7:00 ` [PATCH 05/11] Input: psmouse - fix new device detection logic Chris Wright
2006-06-02  7:00 ` [PATCH 06/11] ohci1394, sbp2: fix "scsi_add_device failed" with PL-3507 based devices Chris Wright
2006-06-02  7:00 ` [PATCH 07/11] the latest consensus libata resume fix Chris Wright
2006-06-02 19:50   ` Jens Axboe
2006-06-02 20:02     ` Greg KH
2006-06-02 20:02     ` Chris Wright [this message]
2006-06-03  8:49     ` Marcel Holtmann
2006-06-03 13:22       ` Jens Axboe
2006-06-03 17:41         ` Chris Wright
2006-06-02  7:00 ` [PATCH 08/11] ipw2200: Filter unsupported channels out in ad-hoc mode Chris Wright
2006-06-02  7:00 ` [PATCH 09/11] x86_64: x86_64 add crashdump trigger points Chris Wright
2006-06-02  7:00 ` [PATCH 10/11] x86_64: Dont do syscall exit tracing twice Chris Wright
2006-06-02  7:00 ` [PATCH 11/11] sbp2: backport read_capacity workaround for iPod Chris Wright

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=20060602200244.GS18769@moss.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=axboe@suse.de \
    --cc=chuckw@quantumlinux.com \
    --cc=davej@redhat.com \
    --cc=gregkh@suse.de \
    --cc=jeff@garzik.org \
    --cc=jmforbes@linuxtx.org \
    --cc=liml@rtr.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=rdunlap@xenotime.net \
    --cc=reviews@ml.cw.f00f.org \
    --cc=stable@kernel.org \
    --cc=torvalds@osdl.org \
    --cc=tytso@mit.edu \
    --cc=zwane@arm.linux.org.uk \
    /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