mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: linux-kernel@vger.kernel.org
Cc: Andi Kleen <ak@linux.intel.com>, dan.j.williams@intel.com
Subject: [PATCH 5/5] Avoid section type conflict in dma/ioat/dma_v3.c
Date: Tue,  7 Jun 2011 15:26:33 -0700	[thread overview]
Message-ID: <1307485593-27196-5-git-send-email-andi@firstfloor.org> (raw)
In-Reply-To: <1307485593-27196-1-git-send-email-andi@firstfloor.org>

From: Andi Kleen <ak@linux.intel.com>

const __read_mostly is not legal and causes section type conflicts.
That's because the read.mostly section is not read only.
Simply drop the const for the read mostly fields.

Cc: dan.j.williams@intel.com
Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
 drivers/dma/ioat/dma_v3.c |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/dma/ioat/dma_v3.c b/drivers/dma/ioat/dma_v3.c
index d845dc4..e1e052a 100644
--- a/drivers/dma/ioat/dma_v3.c
+++ b/drivers/dma/ioat/dma_v3.c
@@ -73,10 +73,10 @@
 /* provide a lookup table for setting the source address in the base or
  * extended descriptor of an xor or pq descriptor
  */
-static const u8 xor_idx_to_desc __read_mostly = 0xd0;
-static const u8 xor_idx_to_field[] __read_mostly = { 1, 4, 5, 6, 7, 0, 1, 2 };
-static const u8 pq_idx_to_desc __read_mostly = 0xf8;
-static const u8 pq_idx_to_field[] __read_mostly = { 1, 4, 5, 0, 1, 2, 4, 5 };
+static u8 xor_idx_to_desc __read_mostly = 0xd0;
+static u8 xor_idx_to_field[] __read_mostly = { 1, 4, 5, 6, 7, 0, 1, 2 };
+static u8 pq_idx_to_desc __read_mostly = 0xf8;
+static u8 pq_idx_to_field[] __read_mostly = { 1, 4, 5, 0, 1, 2, 4, 5 };
 
 static dma_addr_t xor_get_src(struct ioat_raw_descriptor *descs[2], int idx)
 {
-- 
1.7.4.4


  parent reply	other threads:[~2011-06-07 22:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07 22:26 [PATCH 1/5] SH: drop const from io port variiable Andi Kleen
2011-06-07 22:26 ` [PATCH 2/5] Fix mismatched variable in rcutree_trace.c Andi Kleen
2011-06-07 22:42   ` Thomas Gleixner
2011-06-07 23:13     ` Paul E. McKenney
2011-06-07 23:43       ` Andi Kleen
2011-06-08  0:13         ` Paul E. McKenney
2011-06-07 22:26 ` [PATCH 3/5] IRDA: Fix global type conflicts in net/irda/irsysctl.c Andi Kleen
2011-06-09  7:29   ` David Miller
2011-06-07 22:26 ` [PATCH 4/5] ixgbe: Fix incorrect declaration of ixgbevf_mbx_ops Andi Kleen
2011-06-07 22:56   ` Rose, Gregory V
2011-06-08 19:04     ` Jeff Kirsher
2011-06-07 22:26 ` Andi Kleen [this message]
2011-06-07 23:07   ` [PATCH 5/5] Avoid section type conflict in dma/ioat/dma_v3.c Dan Williams

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=1307485593-27196-5-git-send-email-andi@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=ak@linux.intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome