linux-kernel - Re: [PATCH v1.0 16/16] arcmsr: support new adapter ARC12x4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140502093418.GH4963@mwanda>
Date:	Fri, 2 May 2014 12:34:18 +0300
From:	Dan Carpenter <dan.carpenter@...cle.com>
To:	ching <ching2048@...ca.com.tw>
Cc:	jbottomley@...allels.com, thenzl@...hat.com,
	linux-scsi@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1.0 16/16] arcmsr: support new adapter ARC12x4

On Wed, Apr 30, 2014 at 07:46:18PM +0800, ching wrote:
> +	acb->pmuD = reg;
> +	reg->chip_id = (u32 __iomem *)((unsigned long)acb->mem_base0 +
> +		ARCMSR_ARC1214_CHIP_ID);
> +	reg->cpu_mem_config = (u32 __iomem *)((unsigned long)
> +		acb->mem_base0 + ARCMSR_ARC1214_CPU_MEMORY_CONFIGURATION);

These casts aren't needed because acb->mem_base0 is a void __iomem *.
You could just do:

	reg->cpu_mem_config = acb->mem_base0 + ARCMSR_ARC1214_CPU_MEMORY_CONFIGURATION;

Or you could change ARCMSR_ARC1214_CPU_MEMORY_CONFIGURATION to:

#define ARCMSR_ARC1214_CPU_MEMORY_CONFIGURATION(acb) (acb->mem_base0 + 0x00008)

So it would be:

	reg->cpu_mem_config = ARCMSR_ARC1214_CPU_MEMORY_CONFIGURATION(acb);


> +	reg->i2o_host_interrupt_mask = (u32 __iomem *)((unsigned long)
> +		acb->mem_base0 + ARCMSR_ARC1214_I2_HOST_INTERRUPT_MASK);
> +	reg->sample_at_reset = (u32 __iomem *)((unsigned long)
> +		acb->mem_base0 + ARCMSR_ARC1214_SAMPLE_RESET);
> +	reg->reset_request = (u32 __iomem *)((unsigned long)

regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/