cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] RHEL fix for bz428751 try 2
Date: Thu, 13 Mar 2008 09:16:32 +0000	[thread overview]
Message-ID: <1205399792.3635.46.camel@quoit> (raw)
In-Reply-To: <20080313045451.GA3173@ether.msp.redhat.com>

Hi,

On Wed, 2008-03-12 at 23:54 -0500, Benjamin Marzinski wrote:
> Here is a second version of the cluster coherency patch.  It hasn't been
> tested heavily, since it relies on 432075, and there's not complete fix
> for that yet, but it have been able to run the tests coherency test
> from the bugzilla to completion.  This version still has the extra
> include file so that it can tested seperately from the kernel.
> 
> -Ben

The patch looks good, but can you put the two new constants into
lm_interface.h? I know that we need that for RHEL, but I'd rather not
add another header in upstream,

Steve.




      reply	other threads:[~2008-03-13  9:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13  4:54 [Cluster-devel] [PATCH] RHEL fix for bz428751 try 2 Benjamin Marzinski
2008-03-13  9:16 ` Steven Whitehouse [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=1205399792.3635.46.camel@quoit \
    --to=swhiteho@redhat.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;
as well as URLs for NNTP newsgroup(s).