linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Freemyer <greg.freemyer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Mark Lord <kernel-R6A+fiHC8nRWk0Htik3J/w@public.gmane.org>
Cc: Thomas Hertweck <Thomas.Hertweck-S0/GAf8tV78@public.gmane.org>,
	opensuse-kernel-stAJ6ESoqRxg9hUCZPvPmw@public.gmane.org,
	IDE/ATA development list
	<linux-ide-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: SSD / filesystem / TRIM
Date: Tue, 31 Aug 2010 12:05:26 -0400	[thread overview]
Message-ID: <AANLkTin+bc8vw0cpqaYeP6GNUe-ioxMTTy5CXC9ZquRf@mail.gmail.com> (raw)
In-Reply-To: <4C7CFDFD.5000902-R6A+fiHC8nRWk0Htik3J/w@public.gmane.org>

On Tue, Aug 31, 2010 at 9:05 AM, Mark Lord <kernel-R6A+fiHC8nRWk0Htik3J/w@public.gmane.org> wrote:
> On 10-08-31 08:51 AM, Greg Freemyer wrote:
>>
>> Does hdparm v.9.30 have any known kernel dependencies that would keep
>> it from working with 2.6.31?
>>
>> Or any other known issues that would argue against opensuse pushing it
>> out as a software update for 11.2 and 11.3?
>>
>> Or at least putting it in a OBS repo so people using wiper.sh/hdparm
>> can use the latest if they load if from the repo..
>
>
> No issues that I know about.
> My own opinion, is that _anyone_ using hdparm should be using v9.30.
>
> Cheers

Mark, Thanks

Thomas, I opened a bugzilla about it:
https://bugzilla.novell.com/show_bug.cgi?id=635920

I hope you'll add yourself as a cc: and test hdparm v9.30 if and when
it is available for test.

Thanks
Greg

      parent reply	other threads:[~2010-08-31 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C759825.60503@web.de>
     [not found] ` <AANLkTimrOOPExu+hU9wNubT3wgJWwUxMwjREn2p=x-qT@mail.gmail.com>
     [not found]   ` <4C7A2949.8070606@web.de>
2010-08-30 19:14     ` [opensuse-kernel] SSD / filesystem / TRIM Greg Freemyer
2010-08-31 12:36       ` Mark Lord
2010-08-31 12:51         ` Greg Freemyer
2010-08-31 13:05           ` Mark Lord
     [not found]             ` <4C7CFDFD.5000902-R6A+fiHC8nRWk0Htik3J/w@public.gmane.org>
2010-08-31 16:05               ` Greg Freemyer [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=AANLkTin+bc8vw0cpqaYeP6GNUe-ioxMTTy5CXC9ZquRf@mail.gmail.com \
    --to=greg.freemyer-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=Thomas.Hertweck-S0/GAf8tV78@public.gmane.org \
    --cc=kernel-R6A+fiHC8nRWk0Htik3J/w@public.gmane.org \
    --cc=linux-ide-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=opensuse-kernel-stAJ6ESoqRxg9hUCZPvPmw@public.gmane.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).