From: jane@oracle.com
Date: Mon, 5 Jun 2017 14:32:10 -0700
> Is it okay to ignore the checkpatch.pl warning in this case?
I absolutely think you can ignore this warning.
Thanks.
Hi,
I have a question about a checkpatch.pl warning against the
use of NR_CPUS -
$ ./scripts/checkpatch.pl diff.patch
WARNING: usage of NR_CPUS is often wrong - consider using
cpu_possible(), num_possible_cpus(), for_each_possible_cpu(), etc
#14: FILE: arch/sparc/kernel/irq_64.c:1039:
+
Hi, David,
On 06/04/2017 04:46 PM, David Miller wrote:
From: Jane Chu
Date: Thu, 1 Jun 2017 15:39:13 -0600
diff --git a/arch/sparc/kernel/irq_64.c b/arch/sparc/kernel/irq_64.c
index 4d0248a..5b19108 100644
--- a/arch/sparc/kernel/irq_64.c
+++ b/arch/sparc/kernel/irq_64.c
@@ -1034,12 +1034,1
From: Jane Chu
Date: Thu, 1 Jun 2017 15:39:13 -0600
> diff --git a/arch/sparc/kernel/irq_64.c b/arch/sparc/kernel/irq_64.c
> index 4d0248a..5b19108 100644
> --- a/arch/sparc/kernel/irq_64.c
> +++ b/arch/sparc/kernel/irq_64.c
> @@ -1034,12 +1034,12 @@ static void __init init_cpu_send_mondo_info(s
Linux SPARC64 limits NR_CPUS to 4064 because init_cpu_send_mondo_info()
only allocates a single page for NR_CPUS mondo entries. Thus we cannot
use all 4096 CPUs on some SPARC platforms.
To fix, allocate (2^order) pages where order is set according to the size
of cpu_list for possible cpus. Since c
5 matches
Mail list logo