From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] fs/dlm/rcom.c: included member.h twice
Date: Thu, 16 Feb 2012 15:21:37 -0500 [thread overview]
Message-ID: <20120216202137.GA4231@redhat.com> (raw)
In-Reply-To: <1329400521-31738-1-git-send-email-danny.kukawka@bisect.de>
On Thu, Feb 16, 2012 at 02:55:21PM +0100, Danny Kukawka wrote:
> fs/dlm/rcom.c included 'member.h' twice, remove the duplicate.
I'll fold this into the current patch I'm working on.
>
> Signed-off-by: Danny Kukawka <danny.kukawka@bisect.de>
> ---
> fs/dlm/rcom.c | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/fs/dlm/rcom.c b/fs/dlm/rcom.c
> index ac5c616..3464d6c 100644
> --- a/fs/dlm/rcom.c
> +++ b/fs/dlm/rcom.c
> @@ -23,7 +23,6 @@
> #include "memory.h"
> #include "lock.h"
> #include "util.h"
> -#include "member.h"
>
>
> static int rcom_response(struct dlm_ls *ls)
> --
> 1.7.8.3
parent reply other threads:[~2012-02-16 20:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1329400521-31738-1-git-send-email-danny.kukawka@bisect.de>]
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=20120216202137.GA4231@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 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).