linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Frans de Boer <frans@fransdb.nl>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: SATA_SIL
Date: Thu, 01 Nov 2007 08:40:31 +0900	[thread overview]
Message-ID: <4729126F.1000108@gmail.com> (raw)
In-Reply-To: <1193781389.26314.9.camel@ws1.fransdb.nl>

Frans de Boer wrote:
> Dear Sir,
> 
> I know, I am not the only one to find out that we can't upgrade to a
> newer kernel when using SUSE 10.3. It seems that in 2.6.23 the sil
> modules have been updated (newer versions) and thus render the current
> system mostly unuseable. I noticed that in the sata_sil24.c source there
> where a significant number of chances, which are probally not easy to
> change. Overwriting the newer versions with the versions from 2.6.22.9
> might work, but for how long.

Those are backported PMP changes and the code base very similar to
2.6.24-rc1.

> Is this a problem SUSE introduced, you forgot to take legacy into
> account or is it a "feature".
> Is this problem adjusted in 2.6.24-rc1?

Please file a bug report at bugzilla.novell.com, attach
/var/log/boot.msg and the result of "hwinfo --all" and assign it to
teheo@novell.com.

Thanks.

-- 
tejun

  parent reply	other threads:[~2007-10-31 23:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-30 21:56 SATA_SIL Frans de Boer
2007-10-30 22:20 ` SATA_SIL Alan Cox
2007-10-30 22:58 ` SATA_SIL Greg Freemyer
2007-10-31 23:40 ` Tejun Heo [this message]
     [not found]   ` <1193955948.17609.31.camel@ws1.fransdb.nl>
2007-11-02  1:11     ` SATA_SIL Tejun Heo
2007-11-02 10:23       ` SATA_SIL Frans de Boer
2007-11-02 10:49         ` SATA_SIL Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2006-11-30  0:18 sata_sil Harold Lee

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=4729126F.1000108@gmail.com \
    --to=htejun@gmail.com \
    --cc=frans@fransdb.nl \
    --cc=jgarzik@pobox.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).