From: Kyle McMartin <kyle@mcmartin.ca>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH] mbx: Fix up duplicate defines in reg_bits.h
Date: Thu, 20 Dec 2007 22:23:58 -0500 [thread overview]
Message-ID: <20071221032358.GD8535@fattire.cabal.ca> (raw)
In-Reply-To: <alpine.LFD.0.9999.0712201731010.21557@woody.linux-foundation.org>
Otherwise patch gets horribly confused and falls over applying
the diff. Not sure why these were being defined twice.
Signed-off-by: Kyle McMartin <kmcmartin@redhat.com>
---
Well, we can get it fixed for -git1, I respun the patch-2.6.24-rc6 diff
with git diff -p v2.6.23..HEAD and applied it to a pristine linux-2.6.23
tree without issue.
cheers,
Kyle
drivers/video/mbx/reg_bits.h | 24 ------------------------
1 files changed, 0 insertions(+), 24 deletions(-)
diff --git a/drivers/video/mbx/reg_bits.h b/drivers/video/mbx/reg_bits.h
index 5f14b4b..8dc4283 100644
--- a/drivers/video/mbx/reg_bits.h
+++ b/drivers/video/mbx/reg_bits.h
@@ -540,30 +540,6 @@
#define DINTRE_HBLNK1_EN (1 << 1)
#define DINTRE_HBLNK0_EN (1 << 0)
-/* DINTRS - Display Interrupt Status Register */
-#define DINTRS_CUR_OR_S (1 << 18)
-#define DINTRS_STR2_OR_S (1 << 17)
-#define DINTRS_STR1_OR_S (1 << 16)
-#define DINTRS_CUR_UR_S (1 << 6)
-#define DINTRS_STR2_UR_S (1 << 5)
-#define DINTRS_STR1_UR_S (1 << 4)
-#define DINTRS_VEVENT1_S (1 << 3)
-#define DINTRS_VEVENT0_S (1 << 2)
-#define DINTRS_HBLNK1_S (1 << 1)
-#define DINTRS_HBLNK0_S (1 << 0)
-
-/* DINTRE - Display Interrupt Enable Register */
-#define DINTRE_CUR_OR_EN (1 << 18)
-#define DINTRE_STR2_OR_EN (1 << 17)
-#define DINTRE_STR1_OR_EN (1 << 16)
-#define DINTRE_CUR_UR_EN (1 << 6)
-#define DINTRE_STR2_UR_EN (1 << 5)
-#define DINTRE_STR1_UR_EN (1 << 4)
-#define DINTRE_VEVENT1_EN (1 << 3)
-#define DINTRE_VEVENT0_EN (1 << 2)
-#define DINTRE_HBLNK1_EN (1 << 1)
-#define DINTRE_HBLNK0_EN (1 << 0)
-
/* DLSTS - display load status register */
#define DLSTS_RLD_ADONE (1 << 23)
--
1.5.3.6
next prev parent reply other threads:[~2007-12-21 3:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 1:41 Linux 2.6.24-rc6 Linus Torvalds
2007-12-21 2:40 ` Zhang, Yanmin
2007-12-21 2:48 ` Kyle McMartin
2007-12-21 3:01 ` Kyle McMartin
2007-12-21 3:49 ` Linus Torvalds
2007-12-21 3:50 ` Kyle McMartin
2007-12-21 4:22 ` Linus Torvalds
2007-12-21 4:40 ` Linus Torvalds
2007-12-21 4:50 ` Kyle McMartin
2007-12-21 4:58 ` Linus Torvalds
2007-12-21 5:21 ` Linus Torvalds
2007-12-21 17:45 ` Linus Torvalds
2007-12-21 16:56 ` Junio C Hamano
2007-12-21 3:23 ` Kyle McMartin [this message]
2007-12-23 0:05 ` S.Çağlar Onur
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=20071221032358.GD8535@fattire.cabal.ca \
--to=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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.