From: Eric Sandeen <sandeen@sandeen.net>
To: Timothy Shimmin <tes@sgi.com>
Cc: "Stephen C. Rigler" <srigler@marathonoil.com>, xfs@oss.sgi.com
Subject: Re: RHEL 4 Compatible Kernel Module Code
Date: Tue, 14 Nov 2006 08:43:39 -0600 [thread overview]
Message-ID: <4559D61B.3060302@sandeen.net> (raw)
In-Reply-To: <30F3263F8874E466D6206C56@timothy-shimmins-power-mac-g5.local>
Timothy Shimmin wrote:
> Hi Eric,
> If you are referring to Mandy's incore extent changes,
> I don't see them in sles9 or sles10.
>
> Having a quick look she has about 5 Mods.
Ok, that's what I thought... pretty big change for a stable branch. Though I'm
surprised that it's not in sles10!
I do have an updated rhel4 module rpm going now; there were about 8 more patches
that the sgi guys deemed worthy for sles9, so I merged them in. Tidying up the
specfile and need to do some tests; if anyone wants a preview, let me know
off-list. I hope to get it tested & available in a day or two.
-Eric
prev parent reply other threads:[~2006-11-14 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 16:10 RHEL 4 Compatible Kernel Module Code Stephen C. Rigler
2006-11-13 18:09 ` Eric Sandeen
2006-11-14 6:42 ` Timothy Shimmin
2006-11-14 14:43 ` Eric Sandeen [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=4559D61B.3060302@sandeen.net \
--to=sandeen@sandeen.net \
--cc=srigler@marathonoil.com \
--cc=tes@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox