public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Reminder for feature libata spindown skipping and warning removal date Dec 2008
Date: Fri, 03 Jul 2009 11:49:37 +0900	[thread overview]
Message-ID: <4A4D71C1.9080608@kernel.org> (raw)
In-Reply-To: <1246587338.2530.17.camel@jaswinder.satnam>

Jaswinder Singh Rajput wrote:
> Hello Tejun,
> 
> What: libata spindown skipping and warning
> When: Dec 2008
> Why:  Some halt(8) implementations synchronize caches for and spin
>       down libata disks because libata didn't use to spin down disk on
>       system halt (only synchronized caches).
>       Spin down on system halt is now implemented.  sysfs node
>       /sys/class/scsi_disk/h:c:i:l/manage_start_stop is present if
>       spin down support is available.
>       Because issuing spin down command to an already spun down disk
>       makes some disks spin up just to spin down again, libata tracks
>       device spindown status to skip the extra spindown command and
>       warn about it.
>       This is to give userspace tools the time to get updated and will
>       be removed after userspace is reasonably updated.
> Who:  Tejun Heo <htejun@gmail.com>
> 
> If you are facing any issue regarding feature removal kindly update the
> "Documentation/feature-removal-schedule.txt" like what you are waiting
> for.

Thanks for the reminder.  Just sent out patch to kill the feature.  :-)

-- 
tejun

      reply	other threads:[~2009-07-03  2:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-03  2:15 Reminder for feature libata spindown skipping and warning removal date Dec 2008 Jaswinder Singh Rajput
2009-07-03  2:49 ` Tejun Heo [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=4A4D71C1.9080608@kernel.org \
    --to=tj@kernel.org \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@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