All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] Fix cvs HEAD kernel modules to build with 2.6.22-rc*
Date: Wed, 6 Jun 2007 08:45:49 -0500	[thread overview]
Message-ID: <20070606134549.GB12231@redhat.com> (raw)
In-Reply-To: <4666B9FA.3060805@ubuntu.com>

On Wed, Jun 06, 2007 at 03:43:22PM +0200, Fabio Massimo Di Nitto wrote:
> David Teigland wrote:
> >
> >Ack, I have the same patch sitting here, but do we want to wait for 2.6.22
> >to be released to apply it?  In the past we've said that HEAD compiles
> >against the latest released kernel, which is still .21.  I don't really
> >care which way we go.
> >
> >Dave
> 
> Well we need .22-nmw to build userland anyway due to the libdlm changes..
> and how i figured we might as well fix the kernel modules.

Ah, right, in that case there's no reason not to check it in.



      reply	other threads:[~2007-06-06 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06  7:38 [Cluster-devel] [PATCH] Fix cvs HEAD kernel modules to build with 2.6.22-rc* Fabio Massimo Di Nitto
2007-06-06 13:39 ` David Teigland
2007-06-06 13:43   ` Fabio Massimo Di Nitto
2007-06-06 13:45     ` David Teigland [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=20070606134549.GB12231@redhat.com \
    --to=teigland@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 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.