linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: Daniel Drake <dsd@gentoo.org>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] libata: track spindown status and skip spindown_compat if possible
Date: Wed, 16 May 2007 01:22:12 -0400	[thread overview]
Message-ID: <464A9504.1020405@garzik.org> (raw)
In-Reply-To: <46498B82.1030802@gmail.com>

Tejun Heo wrote:
> Our assumption that most distros issue STANDBYNOW seems wrong.  The
> upstream sysvinit and thus many distros including gentoo and opensuse
> don't take any action for libata disks on spindown.  We can skip
> compat handling for these distros so that they don't need to update
> anything to take advantage of kernel-side shutdown.
> 
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> ---
> 
> This patch is generated on top of fix-shutdown-warning-message-printing.
> 
>   http://article.gmane.org/gmane.linux.ide/18823
> 
> Jeff, I think we can avoid a lot of problems with this.  Those distros
> which didn't do anything on shutdown would still cause emergency
> unload on older kernels but at least it isn't a regression and things
> should just work on newer kernels.
> 
> If you ack this, I'll update the shutdown.html page accordingly.
> Thanks.

applied to #upstream-fixes



      parent reply	other threads:[~2007-05-16  5:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 10:29 [PATCH] libata: track spindown status and skip spindown_compat if possible Tejun Heo
2007-05-15 11:53 ` Francesco Pretto
2007-05-15 12:03   ` Tejun Heo
2007-05-15 12:12     ` Stephen Clark
2007-05-15 12:17       ` Tejun Heo
2007-05-15 16:44     ` Francesco Pretto
2007-05-16  5:22 ` Jeff Garzik [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=464A9504.1020405@garzik.org \
    --to=jeff@garzik.org \
    --cc=dsd@gentoo.org \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).