Cluster-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] avoid configure failure with F10's 2.6.27.21 kernel headers
Date: Sun, 21 Jun 2009 09:49:37 +0200	[thread overview]
Message-ID: <87vdmqqb5a.fsf@meyering.net> (raw)
In-Reply-To: <20090620102240.GA23581@sucs.org> (Andrew Price's message of "Sat, 20 Jun 2009 11:22:40 +0100")

Andrew Price wrote:
> Which branch is this for? It doesn't apply to gfs2-utils.git...

Hi Andrew,

This is for dlm.
Sorry for not specifying.

I've just done the following to a few cluster-related repositories
so now dlm-related patches will use "[PATCH dlm]" as the prefix:

  git config format.subjectprefix 'PATCH '$(basename $PWD)

> On Fri, Jun 19, 2009 at 08:26:47PM +0200, Jim Meyering wrote:
>> Without the patch below, ./configure would fail like this on Fedora 10:
>>
>>   checking linux/dlm_plock.h usability... no
>>   checking linux/dlm_plock.h presence... yes
>>   configure: WARNING: linux/dlm_plock.h: present but cannot be compiled
...
>> Here's the patch:
>>
>> >From 013d711c8731da4f11df2437c6c1251d7edb91ea Mon Sep 17 00:00:00 2001
>> From: Jim Meyering <meyering@redhat.com>
>> Date: Fri, 19 Jun 2009 20:24:18 +0200
>> Subject: [PATCH] avoid configure failure with F10's 2.6.27.21 kernel headers
...



  reply	other threads:[~2009-06-21  7:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19 18:26 [Cluster-devel] [PATCH] avoid configure failure with F10's 2.6.27.21 kernel headers Jim Meyering
2009-06-20 10:22 ` Andrew Price
2009-06-21  7:49   ` Jim Meyering [this message]
2009-06-20 12:43 ` Fabio M. Di Nitto
2009-06-25 17:30   ` Jim Meyering

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=87vdmqqb5a.fsf@meyering.net \
    --to=jim@meyering.net \
    /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