[PATCH V6 5/9] irqchip/gic: Isolate early GIC initialisation code

2016-06-07 Thread Jon Hunter
To re-use the code that initialises the GIC (found in __gic_init_bases()), from within a platform driver, it is necessary to move the code from the __init section so that it is always present and not removed. Unfortunately, it is not possible to simply drop the __init from the function declaration

[PATCH V5 5/9] irqchip/gic: Isolate early GIC initialisation code

2016-06-06 Thread Jon Hunter
To re-use the code that initialises the GIC (found in __gic_init_bases()), from within a platform driver, it is necessary to move the code from the __init section so that it is always present and not removed. Unfortunately, it is not possible to simply drop the __init from the function declaration

[PATCH V4 5/9] irqchip/gic: Isolate early GIC initialisation code

2016-05-12 Thread Jon Hunter
To re-use the code that initialises the GIC (found in __gic_init_bases()), from within a platform driver, it is necessary to move the code from the __init section so that it is always present and not removed. Unfortunately, it is not possible to simply drop the __init from the function declaration

[PATCH v5 19/32] scsi: hisi_sas: add v1 HW initialisation code

2015-11-17 Thread John Garry
Signed-off-by: John Garry --- drivers/scsi/hisi_sas/hisi_sas.h | 1 + drivers/scsi/hisi_sas/hisi_sas_main.c | 4 + drivers/scsi/hisi_sas/hisi_sas_v1_hw.c | 337 + 3 files changed, 342 insertions(+) diff --git a/drivers/scsi/hisi_sas/hisi_sas.h b/drivers

[PATCH v4 19/32] scsi: hisi_sas: add v1 HW initialisation code

2015-11-16 Thread John Garry
Signed-off-by: John Garry --- drivers/scsi/hisi_sas/hisi_sas.h | 1 + drivers/scsi/hisi_sas/hisi_sas_main.c | 4 + drivers/scsi/hisi_sas/hisi_sas_v1_hw.c | 337 + 3 files changed, 342 insertions(+) diff --git a/drivers/scsi/hisi_sas/hisi_sas.h b/drivers

[PATCH v3 19/32] scsi: hisi_sas: add v1 HW initialisation code

2015-11-09 Thread John Garry
Signed-off-by: John Garry --- drivers/scsi/hisi_sas/hisi_sas.h | 1 + drivers/scsi/hisi_sas/hisi_sas_main.c | 4 + drivers/scsi/hisi_sas/hisi_sas_v1_hw.c | 337 + 3 files changed, 342 insertions(+) diff --git a/drivers/scsi/hisi_sas/hisi_sas.h b/drivers

[PATCH v2 19/32] scsi: hisi_sas: add v1 HW initialisation code

2015-10-26 Thread John Garry
Signed-off-by: John Garry --- drivers/scsi/hisi_sas/hisi_sas.h | 1 + drivers/scsi/hisi_sas/hisi_sas_main.c | 4 + drivers/scsi/hisi_sas/hisi_sas_v1_hw.c | 331 + 3 files changed, 336 insertions(+) diff --git a/drivers/scsi/hisi_sas/hisi_sas.h b/drivers

Re: [PATCH 12/25] scsi: hisi_sas: add v1 HW initialisation code

2015-10-13 Thread Arnd Bergmann
On Tuesday 13 October 2015 13:44:26 John Garry wrote: > Hello, > > Just to be clear, are you saying that you would prefer hisi_sas_probe() > and struct hisi_sas_driver to be relocated to hisi_sas_v1_hw.c? Correct. > I wanted to keep hisi_sas_v1_hw.c containing only code which accesses HW. > >

Re: [PATCH 12/25] scsi: hisi_sas: add v1 HW initialisation code

2015-10-13 Thread John Garry
On 12/10/2015 19:46, Arnd Bergmann wrote: On Monday 12 October 2015 23:20:24 John Garry wrote: @@ -387,6 +392,21 @@ static int hisi_sas_probe(struct platform_device *pdev) } hisi_sas_init_add(hisi_hba); + + rc = hw_init_v1_hw(hisi_hba); + if (rc) + go

Re: [PATCH 12/25] scsi: hisi_sas: add v1 HW initialisation code

2015-10-12 Thread Arnd Bergmann
On Monday 12 October 2015 23:20:24 John Garry wrote: > @@ -387,6 +392,21 @@ static int hisi_sas_probe(struct platform_device *pdev) > } > > hisi_sas_init_add(hisi_hba); > + > + rc = hw_init_v1_hw(hisi_hba); > + if (rc) > + goto err_out_ha; > + > + r

Re: [PATCH] Break out memory initialisation code from page_alloc.c to mem_init.c

2006-11-30 Thread Mel Gorman
On Wed, 29 Nov 2006, Andrew Morton wrote: On Wed, 29 Nov 2006 18:00:47 + [EMAIL PROTECTED] (Mel Gorman) wrote: page_alloc.c contains a large amount of memory initialisation code which obscures the purpose of the file. This patch breaks out the initialisation code into a separate file to

Re: [PATCH] Break out memory initialisation code from page_alloc.c to mem_init.c

2006-11-29 Thread Andrew Morton
On Wed, 29 Nov 2006 18:00:47 + [EMAIL PROTECTED] (Mel Gorman) wrote: > page_alloc.c contains a large amount of memory initialisation code which > obscures the purpose of the file. This patch breaks out the initialisation > code into a separate file to make page_alloc.c a bit easie

Re: initialisation code

2001-03-21 Thread Manoj Sontakke
Hi Thanks for all the help. On Wed, 21 Mar 2001, Keith Owens wrote: > On Wed, 21 Mar 2001 22:00:51 +0530 (IST), > Manoj Sontakke <[EMAIL PROTECTED]> wrote: > > I have a initlisation function (just like pktsched_init in > >TC). Can anyone tell me, where in the kernel boot sequence sh

Re: initialisation code

2001-03-21 Thread Keith Owens
On Thu, 22 Mar 2001 14:59:31 +0530 (IST), Manoj Sontakke <[EMAIL PROTECTED]> wrote: >On Wed, 21 Mar 2001, Keith Owens wrote: >> Welcome to the wonderful world of magic initialisation. >> >> (1) Declare your initialisation function as int __init foo_init(void). >> (2) Decide when your function ne

Re: initialisation code

2001-03-21 Thread Keith Owens
On Wed, 21 Mar 2001 22:00:51 +0530 (IST), Manoj Sontakke <[EMAIL PROTECTED]> wrote: > I have a initlisation function (just like pktsched_init in >TC). Can anyone tell me, where in the kernel boot sequence should I make a >call to my initialisation function. Welcome to the wonderful world o

initialisation code

2001-03-21 Thread Manoj Sontakke
Hi I am trying to implement some QoS in kernel(in the IP layersimilar to TC. BTW TC works in the data-link layer). I am dequeuing the packets from the IP queue when the function ip_forward is called. After processing them, I am reinserting them back to the IP queue. I have