Re: [PATCH 13/25] macintosh/mediabay: add a const qualifier

2012-09-05 Thread Uwe Kleine-König
Hello, On Wed, Sep 05, 2012 at 12:40:17PM +1000, Benjamin Herrenschmidt wrote: > On Mon, 2012-07-23 at 11:13 +0200, Uwe Kleine-König wrote: > > This prepares *of_device_id.data becoming const. Without this change > > the following warning would occur: > > > > drivers/macintosh/mediabay.c: In

RE: [PATCH] DMA/RaidEngine: Enable FSL RaidEngine

2012-09-05 Thread Shi Xuelin-B29237
Hi Dan, Do you have any comments about this RaidEngine patch? Thanks, Forrest -Original Message- From: Linuxppc-dev [mailto:linuxppc-dev-bounces+qiang.liu=freescale@lists.ozlabs.org] On Behalf Of Shi Xuelin-B29237 Sent: 2012年8月22日 14:24 To: dan.j.willi...@gmail.com; vinod.k...@inte

Re: [PATCH v2] powerpc: fix personality handling in ppc64_personality()

2012-09-05 Thread Jiri Kosina
On Wed, 5 Sep 2012, Benjamin Herrenschmidt wrote: > > Directly comparing current->personality against PER_LINUX32 doesn't work > > in cases when any of the personality flags stored in the top three bytes > > are used. > > > > Directly forcefully setting personality to PER_LINUX32 or PER_LINUX > >

[RFC v9 PATCH 07/21] memory-hotplug: call acpi_bus_remove() to remove memory device

2012-09-05 Thread wency
From: Wen Congyang The memory device has been ejected and powoffed, so we can call acpi_bus_remove() to remove the memory device from acpi bus. CC: David Rientjes CC: Jiang Liu CC: Len Brown CC: Benjamin Herrenschmidt CC: Paul Mackerras CC: Christoph Lameter Cc: Minchan Kim CC: Andrew Mor

[RFC v9 PATCH 03/21] memory-hotplug: store the node id in acpi_memory_device

2012-09-05 Thread wency
From: Wen Congyang The memory device has only one node id. Store the node id when enable the memory device, and we can reuse it when removing the memory device. CC: David Rientjes CC: Jiang Liu CC: Len Brown CC: Benjamin Herrenschmidt CC: Paul Mackerras CC: Christoph Lameter Cc: Minchan Ki

[RFC v9 PATCH 09/21] memory-hotplug: does not release memory region in PAGES_PER_SECTION chunks

2012-09-05 Thread wency
From: Yasuaki Ishimatsu Since applying a patch(de7f0cba96786c), release_mem_region() has been changed as called in PAGES_PER_SECTION chunks because register_memory_resource() is called in PAGES_PER_SECTION chunks by add_memory(). But it seems firmware dependency. If CRS are written in the PAGES_P

[RFC v9 PATCH 01/21] memory-hotplug: rename remove_memory() to offline_memory()/offline_pages()

2012-09-05 Thread wency
From: Yasuaki Ishimatsu remove_memory() only try to offline pages. It is called in two cases: 1. hot remove a memory device 2. echo offline >/sys/devices/system/memory/memoryXX/state In the 1st case, we should also change memory block's state, and notify the userspace that the memory block's sta

[RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

2012-09-05 Thread wency
From: Wen Congyang This patch series aims to support physical memory hot-remove. The patches can free/remove the following things: - acpi_memory_info : [RFC PATCH 4/19] - /sys/firmware/memmap/X/{end, start, type} : [RFC PATCH 8/19] - iomem_resource

[RFC v9 PATCH 08/21] memory-hotplug: remove /sys/firmware/memmap/X sysfs

2012-09-05 Thread wency
From: Yasuaki Ishimatsu When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, type} sysfs files are created. But there is no code to remove these files. The patch implements the function to remove them. Note : The code does not free firmware_map_entry since there is no way to

[RFC v9 PATCH 06/21] memory-hotplug: export the function acpi_bus_remove()

2012-09-05 Thread wency
From: Wen Congyang The function acpi_bus_remove() can remove a acpi device from acpi device. When a acpi device is removed, we need to call this function to remove the acpi device from acpi bus. So export this function. CC: David Rientjes CC: Jiang Liu CC: Len Brown CC: Benjamin Herrenschmidt

[RFC v9 PATCH 05/21] memory-hotplug: check whether memory is present or not

2012-09-05 Thread wency
From: Yasuaki Ishimatsu If system supports memory hot-remove, online_pages() may online removed pages. So online_pages() need to check whether onlining pages are present or not. CC: David Rientjes CC: Jiang Liu CC: Len Brown CC: Benjamin Herrenschmidt CC: Paul Mackerras CC: Christoph Lamete

[RFC v9 PATCH 04/21] memory-hotplug: offline and remove memory when removing the memory device

2012-09-05 Thread wency
From: Yasuaki Ishimatsu We should offline and remove memory when removing the memory device. The memory device can be removed by 2 ways: 1. send eject request by SCI 2. echo 1 >/sys/bus/pci/devices/PNP0C80:XX/eject In the 1st case, acpi_memory_disable_device() will be called. In the 2nd case, ac

[RFC v9 PATCH 02/21] memory-hotplug: implement offline_memory()

2012-09-05 Thread wency
From: Wen Congyang The function offline_memory() will be called when hot removing a memory device. The memory device may contain more than one memory block. If the memory block has been offlined, __offline_pages() will fail. So we should try to offline one memory block at a time. If the memory b

[RFC v9 PATCH 20/21] memory-hotplug: clear hwpoisoned flag when onlining pages

2012-09-05 Thread wency
From: Wen Congyang hwpoisoned may set when we offline a page by the sysfs interface /sys/devices/system/memory/soft_offline_page or /sys/devices/system/memory/hard_offline_page. If we don't clear this flag when onlining pages, this page can't be freed, and will not in free list. So we can't offli

[RFC v9 PATCH 15/21] memory-hotplug: implement register_page_bootmem_info_section of sparse-vmemmap

2012-09-05 Thread wency
From: Yasuaki Ishimatsu For removing memmap region of sparse-vmemmap which is allocated bootmem, memmap region of sparse-vmemmap needs to be registered by get_page_bootmem(). So the patch searches pages of virtual mapping and registers the pages by get_page_bootmem(). Note: register_page_bootmem

[RFC v9 PATCH 21/21] memory-hotplug: auto offline page_cgroup when onlining memory block failed

2012-09-05 Thread wency
From: Wen Congyang When a memory block is onlined, we will try allocate memory on that node to store page_cgroup. If onlining the memory block failed, we don't offline the page cgroup, and we have no chance to offline this page cgroup unless the memory block is onlined successfully again. It will

Re: [PATCH 13/25] macintosh/mediabay: add a const qualifier

2012-09-05 Thread Benjamin Herrenschmidt
On Wed, 2012-09-05 at 10:02 +0200, Uwe Kleine-König wrote: > Hello, > > On Wed, Sep 05, 2012 at 12:40:17PM +1000, Benjamin Herrenschmidt wrote: > > On Mon, 2012-07-23 at 11:13 +0200, Uwe Kleine-König wrote: > > > This prepares *of_device_id.data becoming const. Without this change > > > the follow

[RFC v9 PATCH 13/21] memory-hotplug: check page type in get_page_bootmem

2012-09-05 Thread wency
From: Yasuaki Ishimatsu The function get_page_bootmem() may be called more than one time to the same page. There is no need to set page's type, private if the function is not the first time called to the page. Note: the patch is just optimization and does not fix any problem. CC: David Rientjes

[RFC v9 PATCH 10/21] memory-hotplug: add memory_block_release

2012-09-05 Thread wency
From: Yasuaki Ishimatsu When calling remove_memory_block(), the function shows following message at device_release(). Device 'memory528' does not have a release() function, it is broken and must be fixed. remove_memory_block() calls kfree(mem). I think it shouled be called from device_release()

[RFC v9 PATCH 19/21] memory-hotplug: remove sysfs file of node

2012-09-05 Thread wency
From: Wen Congyang This patch introduces a new function try_offline_node() to remove sysfs file of node when all memory sections of this node are removed. If some memory sections of this node are not removed, this function does nothing. CC: David Rientjes CC: Jiang Liu CC: Len Brown CC: Benja

[RFC v9 PATCH 14/21] memory-hotplug: move register_page_bootmem_info_node and put_page_bootmem for sparse-vmemmap

2012-09-05 Thread wency
From: Yasuaki Ishimatsu For implementing register_page_bootmem_info_node of sparse-vmemmap, register_page_bootmem_info_node and put_page_bootmem are moved to memory_hotplug.c CC: David Rientjes CC: Jiang Liu CC: Len Brown CC: Benjamin Herrenschmidt CC: Paul Mackerras CC: Christoph Lameter

[RFC v9 PATCH 11/21] memory-hotplug: remove_memory calls __remove_pages

2012-09-05 Thread wency
From: Yasuaki Ishimatsu The patch adds __remove_pages() to remove_memory(). Then the range of phys_start_pfn argument and nr_pages argument in __remove_pagse() may have different zone. So zone argument is removed from __remove_pages() and __remove_pages() caluculates zone in each section. When C

[RFC v9 PATCH 17/21] memory_hotplug: clear zone when the memory is removed

2012-09-05 Thread wency
From: Yasuaki Ishimatsu When a memory is added, we update zone's and pgdat's start_pfn and spanned_pages in the function __add_zone(). So we should revert these when the memory is removed. Add a new function __remove_zone() to do this. CC: David Rientjes CC: Jiang Liu CC: Len Brown CC: Benjam

[RFC v9 PATCH 16/21] memory-hotplug: free memmap of sparse-vmemmap

2012-09-05 Thread wency
From: Yasuaki Ishimatsu All pages of virtual mapping in removed memory cannot be freed, since some pages used as PGD/PUD includes not only removed memory but also other memory. So the patch checks whether page can be freed or not. How to check whether page can be freed or not? 1. When removing

[RFC v9 PATCH 12/21] memory-hotplug: introduce new function arch_remove_memory()

2012-09-05 Thread wency
From: Wen Congyang We don't call __add_pages() directly in the function add_memory() because some other architecture related things need to be done before or after calling __add_pages(). So we should introduce a new function arch_remove_memory() to revert the things done in arch_add_memory(). No

[RFC v9 PATCH 18/21] memory-hotplug: add node_device_release

2012-09-05 Thread wency
From: Yasuaki Ishimatsu When calling unregister_node(), the function shows following message at device_release(). Device 'node2' does not have a release() function, it is broken and must be fixed. So the patch implements node_device_release() CC: David Rientjes CC: Jiang Liu CC: Len Brown C

Re: [PATCH -V7 04/12] arch/powerpc: Convert virtual address to vpn

2012-09-05 Thread Paul Mackerras
On Tue, Sep 04, 2012 at 02:31:21PM +0530, Aneesh Kumar K.V wrote: > From: "Aneesh Kumar K.V" > > This patch convert different functions to take virtual page number > instead of virtual address. Virtual page number is virtual address > shifted right by VPN_SHIFT (12) bits. This enable us to have a

Re: [PATCH] usb: gadget: fsl_udc_core: remove mapped flag

2012-09-05 Thread Sergei Shtylyov
Hello. On 04-09-2012 21:24, Enrico Scholz wrote: The 'mapped' flag in 'struct fsl_req' flag is redundant with checking for 'req.dma != DMA_ADDR_INVALID' and it was also set to a wrong value (see 2nd hunk of patch). Replacing it in the way described above saves 60 bytes: function

Re: [PATCH] usb: gadget: fsl_udc_core: remove mapped flag

2012-09-05 Thread Felipe Balbi
Hi, On Tue, Sep 04, 2012 at 07:24:59PM +0200, Enrico Scholz wrote: > The 'mapped' flag in 'struct fsl_req' flag is redundant with checking > for 'req.dma != DMA_ADDR_INVALID' and it was also set to a wrong value you should not be using DMA_ADDR_INVALID anymore. Use the generic map/unmap routines

Re: [PATCH -V7 04/12] arch/powerpc: Convert virtual address to vpn

2012-09-05 Thread Aneesh Kumar K.V
Paul Mackerras writes: > On Tue, Sep 04, 2012 at 02:31:21PM +0530, Aneesh Kumar K.V wrote: >> From: "Aneesh Kumar K.V" >> >> This patch convert different functions to take virtual page number >> instead of virtual address. Virtual page number is virtual address >> shifted right by VPN_SHIFT (12

Re: [PATCH V3 1/3] drivers/char/tpm: Add new device driver to support IBM vTPM

2012-09-05 Thread Kent Yoder
On Wed, Sep 05, 2012 at 01:40:07PM +1000, Benjamin Herrenschmidt wrote: > On Wed, 2012-08-22 at 16:42 -0500, Kent Yoder wrote: > > On Wed, Aug 22, 2012 at 04:17:43PM -0500, Ashley Lai wrote: > > > This patch adds a new device driver to support IBM virtual TPM > > > (vTPM) for PPC64. IBM vTPM is su

Re: [PATCH V3 1/3] drivers/char/tpm: Add new device driver to support IBM vTPM

2012-09-05 Thread Ashley Lai
Hi Ben., Thank you so much for the comments. Please see my response below. > > > + */ > > > +static int tpm_ibmvtpm_recv(struct tpm_chip *chip, u8 *buf, size_t count) > > > +{ > > > + struct ibmvtpm_dev *ibmvtpm; > > > + u16 len; > > > + > > > + ibmvtpm = (struct ibmvtpm_dev *)chip->vendor.data;

Re: [PATCH V3 1/3] drivers/char/tpm: Add new device driver to support IBM vTPM

2012-09-05 Thread Benjamin Herrenschmidt
On Wed, 2012-09-05 at 10:46 -0500, Kent Yoder wrote: > On Wed, Sep 05, 2012 at 01:40:07PM +1000, Benjamin Herrenschmidt wrote: > > On Wed, 2012-08-22 at 16:42 -0500, Kent Yoder wrote: > > > On Wed, Aug 22, 2012 at 04:17:43PM -0500, Ashley Lai wrote: > > > > This patch adds a new device driver to su

Re: [PATCH v2] powerpc: fix personality handling in ppc64_personality()

2012-09-05 Thread Benjamin Herrenschmidt
On Wed, 2012-09-05 at 10:56 +0200, Jiri Kosina wrote: > Hi Benjamin, > > actually commit 7256a5d2da56 seems to contain the correct PER_LINUX > handling, so seems like you picked the right one :) > Odd, they looked different around the use of PER_MASK when I looked but I was tired & jet lagged,

Re: [git pull] Please pull powerpc.git merge branch

2012-09-05 Thread Benjamin Herrenschmidt
On Wed, 2012-09-05 at 16:12 +1000, Benjamin Herrenschmidt wrote: > The following changes since commit > 5b716ac728bcc01b1f2a7ed6e437196602237c27: > > Merge branch 'for-next' of git://git.samba.org/sfrench/cifs-2.6 > (2012-09-02 11:30:10 -0700) > > are available in the git repository at: > > >

Re: [PATCH -V7 11/12] arch/powerpc: Add 64TB support

2012-09-05 Thread Paul Mackerras
On Tue, Sep 04, 2012 at 02:31:28PM +0530, Aneesh Kumar K.V wrote: > From: "Aneesh Kumar K.V" > > Increase max addressable range to 64TB. This is not tested on > real hardware yet. > > Signed-off-by: Aneesh Kumar K.V Reviewed-by: Paul Mackerras ___ L

Re: [PATCH -V7 07/12] arch/powerpc: Increase the slice range to 64TB

2012-09-05 Thread Paul Mackerras
On Tue, Sep 04, 2012 at 02:31:24PM +0530, Aneesh Kumar K.V wrote: > From: "Aneesh Kumar K.V" > > This patch makes the high psizes mask as an unsigned char array > so that we can have more than 16TB. Currently we support upto > 64TB > > Signed-off-by: Aneesh Kumar K.V Reviewed-by: Paul Mackerra

Re: [PATCH -V7 12/12] arch/powerpc: Update VSID allocation documentation

2012-09-05 Thread Paul Mackerras
On Tue, Sep 04, 2012 at 02:31:29PM +0530, Aneesh Kumar K.V wrote: > From: "Aneesh Kumar K.V" > > This update the proto-VSID and VSID scramble related information > to be more generic by using names instead of current values. > > Signed-off-by: Aneesh Kumar K.V Reviewed-by: Paul Mackerras

Re: [PATCH -V7 04/12] arch/powerpc: Convert virtual address to vpn

2012-09-05 Thread Paul Mackerras
On Wed, Sep 05, 2012 at 08:15:11PM +0530, Aneesh Kumar K.V wrote: > > One of the reason i avoided va -> vpn rename is to avoid unnecessary > hunks. But then what i can do is to apply the name to those part of the > hunks which is being touched in this patch. Will that help. Or do you > want me to

Re: [powerpc:next 11/29] arch/powerpc/platforms/pseries/iommu.c:1064:2: error: implicit declaration of function 'memblock_end_of_DRAM'

2012-09-05 Thread Benjamin Herrenschmidt
On Thu, 2012-09-06 at 10:20 +0800, Fengguang Wu wrote: > Hi Michael, > > FYI, kernel build failed on > > tree: git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc.git next > head: 8b64a9dfb091f1eca8b7e58da82f1e7d1d5fe0ad > commit: 474e3d569b63f7275cfec072d7ef7b2ffb8904c8 [11/29] powerp

Re: [powerpc:next 11/29] arch/powerpc/platforms/pseries/iommu.c:1064:2: error: implicit declaration of function 'memblock_end_of_DRAM'

2012-09-05 Thread Benjamin Herrenschmidt
On Thu, 2012-09-06 at 12:44 +1000, Benjamin Herrenschmidt wrote: > On Thu, 2012-09-06 at 10:20 +0800, Fengguang Wu wrote: > > Hi Michael, > > > > FYI, kernel build failed on > > > > tree: git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc.git next > > head: 8b64a9dfb091f1eca8b7e58da82

Re: [powerpc:next 24/29] drivers/atm/fore200e.h:263:3: error: redefinition of typedef 'opcode_t' with different type

2012-09-05 Thread Benjamin Herrenschmidt
On Thu, 2012-09-06 at 10:19 +0800, Fengguang Wu wrote: > Hi Ananth, > > FYI, kernel build failed on > > tree: git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc.git next > head: 8b64a9dfb091f1eca8b7e58da82f1e7d1d5fe0ad > commit: 8b7b80b9ebb46dd88fbb94e918297295cf312b59 [24/29] powerpc

Re: [powerpc:next 11/29] arch/powerpc/platforms/pseries/iommu.c:1064:2: error: implicit declaration of function 'memblock_end_of_DRAM'

2012-09-05 Thread Fengguang Wu
On Thu, Sep 06, 2012 at 12:49:14PM +1000, Benjamin Herrenschmidt wrote: > On Thu, 2012-09-06 at 12:44 +1000, Benjamin Herrenschmidt wrote: > > On Thu, 2012-09-06 at 10:20 +0800, Fengguang Wu wrote: > > > Hi Michael, > > > > > > FYI, kernel build failed on > > > > > > tree: git://git.kernel.org/

Re: [powerpc:next 11/29] arch/powerpc/platforms/pseries/iommu.c:1064:2: error: implicit declaration of function 'memblock_end_of_DRAM'

2012-09-05 Thread Benjamin Herrenschmidt
On Thu, 2012-09-06 at 11:03 +0800, Fengguang Wu wrote: > > No problem. Sorry I didn't know that. Will test HEAD commits only for > this branch in future. Actually, I'd rather you continue doing bisection tests, it's good, I can whack on the head of people who submit stuff with breakage. In fact,

Re: [powerpc:next 11/29] arch/powerpc/platforms/pseries/iommu.c:1064:2: error: implicit declaration of function 'memblock_end_of_DRAM'

2012-09-05 Thread Fengguang Wu
On Thu, Sep 06, 2012 at 01:05:56PM +1000, Benjamin Herrenschmidt wrote: > On Thu, 2012-09-06 at 11:03 +0800, Fengguang Wu wrote: > > > > No problem. Sorry I didn't know that. Will test HEAD commits only for > > this branch in future. > > Actually, I'd rather you continue doing bisection tests, it

linux-next: manual merge of the trivial tree with the powerpc tree

2012-09-05 Thread Stephen Rothwell
Hi Jiri, Today's linux-next merge of the trivial tree got a conflict in drivers/scsi/ipr.c between commit d3dbeef657fd ("powerpc: Rename 64-bit PVR constants to PVR_foo") from the powerpc tree and commit 203fa3fe9c9d ("ipr: fix small coding style issues") from the trivial tree. Just context chang

Re: [powerpc:next 24/29] drivers/atm/fore200e.h:263:3: error: redefinition of typedef 'opcode_t' with different type

2012-09-05 Thread David Miller
From: Benjamin Herrenschmidt Date: Thu, 06 Sep 2012 12:56:12 +1000 > (CC'ing Dave and Meelis who from the git history *might* have HW access > to test a possible patch). Hardware isn't necessary, just make sure the resulting binary is identical both before and after the change. _

[PATCH] [v2] sata_fsl: add workaround for data length mismatch on freescale V2 controller

2012-09-05 Thread Shaohui Xie
The freescale V2 SATA controller checks if the received data length matches the programmed length 'ttl', if not, it assumes that this is an error. In ATAPI, the 'ttl' is based on max allocation length and not the actual data transfer length, controller will raise 'DLM' (Data length Mismatch) error

[PATCH 1/5] powerpc: Pack arch_hw_breakpoint to avoid holes in struct

2012-09-05 Thread Michael Neuling
No functional change Signed-off-by: Michael Neuling --- arch/powerpc/include/asm/hw_breakpoint.h |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/powerpc/include/asm/hw_breakpoint.h b/arch/powerpc/include/asm/hw_breakpoint.h index be04330..39b323e 100644 --- a/a

[PATCH 2/5] powerpc: Use consistent name info for arch_hw_breakpoint

2012-09-05 Thread Michael Neuling
Change bp_info to info to be consistent with the rest of this file. Signed-off-by: Michael Neuling --- arch/powerpc/kernel/hw_breakpoint.c |8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/powerpc/kernel/hw_breakpoint.c b/arch/powerpc/kernel/hw_breakpoint.c ind

[PATCH 3/5] powerpc: Use the XDABR hcall

2012-09-05 Thread Michael Neuling
We never use the XDABR hcall since we check for DABR hcall first. XDABR syscall is better since it allows us to also set the DABRX. Signed-off-by: Michael Neuling --- arch/powerpc/platforms/pseries/setup.c |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/powerpc/

[PATCH 4/5] powerpc: Rework set_dabr so it can take a DABRX value as well

2012-09-05 Thread Michael Neuling
Rework set_dabr to take a DABRX value as well. We are not actually changing any functionality at this stage, just preparing for that. The SET_XDABR hcall checks to make sure DABRX is non-zero, and if it is it barfs. So in this case when we are clearing both DABR and DABRX, just set 1 bit to make

[PATCH 5/5] powerpc: Dynamically calculate the dabrx based on kernel/user/hypervisor

2012-09-05 Thread Michael Neuling
Currently we mark the DABRX to interrupt on all matches (hypervisor/kernel/user and then filter in software. We can be a lot smarter now that we can set the DABRX dynamically. This sets the DABRX based on the flags passed by the user. Signed-off-by: Michael Neuling --- arch/powerpc/include/asm

Re: [PATCH 5/5] powerpc: Dynamically calculate the dabrx based on kernel/user/hypervisor

2012-09-05 Thread Michael Neuling
Michael Neuling wrote: > Currently we mark the DABRX to interrupt on all matches > (hypervisor/kernel/user and then filter in software. We can be a lot > smarter now that we can set the DABRX dynamically. > > This sets the DABRX based on the flags passed by the user. > > Signed-off-by: Michael

Re: [PATCH 4/5] powerpc: Rework set_dabr so it can take a DABRX value as well

2012-09-05 Thread Geert Uytterhoeven
On Thu, Sep 6, 2012 at 7:17 AM, Michael Neuling wrote: > Rework set_dabr to take a DABRX value as well. We are not actually > changing any functionality at this stage, just preparing for that. You are changing functionality. > #define DABRX_USER (1UL << 0) > #define DABRX_KERNEL (1UL <<

Re: [powerpc:next 24/29] drivers/atm/fore200e.h:263:3: error: redefinition of typedef 'opcode_t' with different type

2012-09-05 Thread Meelis Roos
> (CC'ing Dave and Meelis who from the git history *might* have HW access > to test a possible patch). I do have the hardware and can test patches, but it usually takes several days until I happen to go where it is and connect the machine. -- Meelis Roos (mr...@linux.ee) ___