From: Emmanuel Florac <eflorac@intellique.com>
To: "Tore Høivaag" <tore.hoivaag.larsen@cggveritas.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>,
Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Subject: Re: Pid: 8345, comm: rsync Not tainted 2.6.32.22intel #1
Date: Tue, 26 Oct 2010 13:47:03 +0200 [thread overview]
Message-ID: <20101026134703.3f06cfda@harpe.intellique.com> (raw)
In-Reply-To: <CFFC47E79E870F4EBAD0CA24D8CD7652ED04A5F7F8@CRW-EXM01.int.cggveritas.com>
Le Tue, 26 Oct 2010 12:30:22 +0100
Larsen, Tore Høivaag <tore.hoivaag.larsen@cggveritas.com> écrivait:
> You should keep the driver and firmware ins sync wither kernel.
> Choose e.g. latest 9.4.3 iso for 2.6.9, and 9.5.3 for
> RHEL5/SLES11/Fedora13. Do not use 9.5.3 firmware with RHEL4/SLES10
> native driver. If I remeber correctly tw_update doesn't even let you
> mix a downgrade driver with new firmware, and vs.versus.
Yes, it will complain in case your driver/api isn't compatible with the
newer firmware. Of course, only actually upgrade if it tells you :
"proceed to update".
However I'm pretty sure 2.6.23 is safe for 4.x firmware (2.6.24
definitely is).
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-10-26 11:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 6:25 Pid: 8345, comm: rsync Not tainted 2.6.32.22intel #1 Stefan Priebe - Profihost AG
2010-10-26 7:22 ` Emmanuel Florac
2010-10-26 7:24 ` Stefan Priebe - Profihost AG
2010-10-26 7:41 ` Emmanuel Florac
2010-10-26 7:53 ` Stefan Priebe - Profihost AG
2010-10-26 11:01 ` Emmanuel Florac
2010-10-26 11:03 ` Stefan Priebe - Profihost AG
2010-10-26 11:25 ` Emmanuel Florac
2010-10-26 12:09 ` Stefan Priebe - Profihost AG
2010-10-26 13:00 ` Emmanuel Florac
2010-10-26 23:23 ` Michael Monnerie
2010-10-27 3:55 ` Dave Chinner
2010-10-27 10:58 ` Michael Monnerie
2010-10-27 20:59 ` Dave Chinner
2010-10-28 9:39 ` Michael Monnerie
2010-10-27 6:04 ` Emmanuel Florac
2010-10-27 7:00 ` Stefan Priebe - Profihost AG
2010-10-27 10:06 ` Emmanuel Florac
2010-10-27 10:08 ` Stefan Priebe - Profihost AG
2010-10-27 10:12 ` Emmanuel Florac
2010-10-27 10:22 ` Stefan Priebe - Profihost AG
2010-10-27 11:14 ` Emmanuel Florac
2010-10-26 11:30 ` Larsen, Tore Høivaag
2010-10-26 11:47 ` Emmanuel Florac [this message]
2010-11-01 8:01 ` Stefan Priebe - Profihost AG
2010-11-01 10:11 ` Emmanuel Florac
2010-11-01 10:28 ` Stefan Priebe - Profihost AG
2010-11-01 12:27 ` Dave Chinner
2010-11-01 12:28 ` Stefan Priebe - Profihost AG
2010-11-01 12:52 ` Dave Chinner
2010-11-01 13:29 ` Emmanuel Florac
2010-11-01 13:48 ` Stefan Priebe - Profihost AG
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=20101026134703.3f06cfda@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=s.priebe@profihost.ag \
--cc=tore.hoivaag.larsen@cggveritas.com \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.