From: Steven Cole <elenstev@mesatop.com>
To: Stephen Lord <lord@sgi.com>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] compile fix for 2.5 kdev_t compatibility macros
Date: 28 Jun 2002 08:37:56 -0600 [thread overview]
Message-ID: <1025275076.27133.131.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <1025272233.1168.21.camel@n236>
On Fri, 2002-06-28 at 07:50, Stephen Lord wrote:
>
>
> Marcelo,
>
> We started using these for XFS, and found a missing bracket, patch
> against 2.4.19-rc1.
>
> Steve
>
> *** linux-2.4.19-rc1/include/linux/kdev_t.h Fri Jun 28 08:40:22 2002
> --- linux/include/linux/kdev_t.h Fri Jun 28 07:05:32 2002
> ***************
> *** 81,87 ****
> #define minor(d) MINOR(d)
> #define kdev_same(a,b) ((a) == (b))
> #define kdev_none(d) (!(d))
> ! #define kdev_val(d) ((unsigned int)(d)
> #define val_to_kdev(d) ((kdev_t(d))
>
> /*
> --- 81,87 ----
> #define minor(d) MINOR(d)
> #define kdev_same(a,b) ((a) == (b))
> #define kdev_none(d) (!(d))
> ! #define kdev_val(d) ((unsigned int)(d))
> #define val_to_kdev(d) ((kdev_t(d))
>
> /*
That's an odd-looking patch. Is this what you meant?
Steven
--- linux-2.4.19-rc1/include/linux/kdev_t.h.orig Fri Jun 28 08:31:27 2002
+++ linux-2.4.19-rc1/include/linux/kdev_t.h Fri Jun 28 08:32:36 2002
@@ -81,7 +81,7 @@
#define minor(d) MINOR(d)
#define kdev_same(a,b) ((a) == (b))
#define kdev_none(d) (!(d))
-#define kdev_val(d) ((unsigned int)(d)
+#define kdev_val(d) ((unsigned int)(d))
#define val_to_kdev(d) ((kdev_t(d))
/*
next prev parent reply other threads:[~2002-06-28 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-28 13:50 Stephen Lord
2002-06-28 14:37 ` Steven Cole [this message]
2002-06-28 14:42 ` Stephen Lord
2002-06-28 15:02 ` Andries Brouwer
2002-06-28 15:10 ` Martin Josefsson
2002-06-28 15:24 ` Steven Cole
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=1025275076.27133.131.camel@spc9.esa.lanl.gov \
--to=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lord@sgi.com \
--cc=marcelo@conectiva.com.br \
/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
all inboxes | Powered by JetHome®