public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 5/5] Avoid section type conflict in dma/ioat/dma_v3.c
Date: Tue, 07 Jun 2011 16:07:17 -0700	[thread overview]
Message-ID: <4DEEAF25.5040104@intel.com> (raw)
In-Reply-To: <1307485593-27196-5-git-send-email-andi@firstfloor.org>

On 6/7/2011 3:26 PM, Andi Kleen wrote:
> 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

Acked-by: Dan Williams <dan.j.williams@intel.com>

I don't have any other ioatdma stuff pending so I'm happy for this to go 
in through another tree.

--
Dan

      reply	other threads:[~2011-06-07 23:07 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 ` [PATCH 5/5] Avoid section type conflict in dma/ioat/dma_v3.c Andi Kleen
2011-06-07 23:07   ` Dan Williams [this message]

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=4DEEAF25.5040104@intel.com \
    --to=dan.j.williams@intel.com \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --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