login
Login
/
Register
Search
Search this site:
Forums
News
Blogs
Features
Site
Home
»
Mailing list archives
»
linux-kernel
»
2008
»
August
»
29
Re: [PATCH] dyn_array: using %pF instead of print_fn_descriptor_symbol
view
thread
Previous message: [
thread
] [
date
] [
author
]
Next message: [
thread
] [
date
] [
author
]
[view in full thread]
From: Andrew Morton
Subject:
Re: [PATCH] dyn_array: using %pF instead of print_fn_descriptor_symbol
Date: Friday, August 29, 2008 - 3:45 pm
On Fri, 29 Aug 2008 15:32:58 -0700 "Yinghai Lu" <yhlu.kernel@gmail.com> wrote:
quoted text
> On Fri, Aug 29, 2008 at 3:20 PM, Andrew Morton > <akpm@linux-foundation.org> wrote: > > On Fri, 29 Aug 2008 15:07:49 -0700 > > Yinghai Lu <yhlu.kernel@gmail.com> wrote: > > > >> + printk(KERN_DEBUG "per_cpu_dyn_array %pF ==> [%#lx - %#lx]\n", > >> + da->name, phys, phys + size); > > > > This: > > > > struct dyn_array { > > void **name; > > > > is a bit confusing. One normally expects a variable called "name" to > > point at a character string. > > > > What _does_ this thing point at? There are no code comments which I > > can find, it's unobvious from the source code, the type is the > > information-free void** and the identifier is misleading. > > > > I find that documenting the data structures is the best way of making > > code understandable (and hence maintainable). > > struct dyn_array { > void **name; > unsigned long size; > unsigned int *nr; > unsigned long align; > void (*init_work)(void *); > }; > extern struct dyn_array *__dyn_array_start[], *__dyn_array_end[]; > extern struct dyn_array *__per_cpu_dyn_array_start[], > *__per_cpu_dyn_array_end[]; > > #define DEFINE_DYN_ARRAY_ADDR(nameX, addrX, sizeX, nrX, alignX, init_workX) \ > static struct dyn_array __dyn_array_##nameX __initdata = \ > { .name = (void **)&(nameX),\ > .size = sizeX,\ > .nr = &(nrX),\ > .align = alignX,\ > .init_work = init_workX,\ > }; \ > static struct dyn_array *__dyn_array_ptr_##nameX __used \ > __attribute__((__section__(".dyn_array.init"))) = \ > &__dyn_array_##nameX > > #define DEFINE_DYN_ARRAY(nameX, sizeX, nrX, alignX, init_workX) \ > DEFINE_DYN_ARRAY_ADDR(nameX, nameX, sizeX, nrX, alignX, init_workX) > > and use is > > struct irq_desc *sparse_irqs; > DEFINE_DYN_ARRAY(sparse_irqs, sizeof(struct irq_desc), nr_irq_desc, > PAGE_SIZE, init_work); > > > then sparse_irqs is pointer, and .name store the address of that pointer. > > later use > *da->name = phys_to_virt(phys); > to take back the dyn address. >
Well yes, I have a copy of that too. Why is it called "name"? --
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/
Previous message: [
thread
] [
date
] [
author
]
Next message: [
thread
] [
date
] [
author
]
Messages in current thread:
[PATCH] dyn_array: using %pF instead of print_fn_descripto ...
, Yinghai Lu
, (Fri Aug 29, 3:07 pm)
Re: [PATCH] dyn_array: using %pF instead of print_fn_descr ...
, Andrew Morton
, (Fri Aug 29, 3:20 pm)
Re: [PATCH] dyn_array: using %pF instead of print_fn_descr ...
, Yinghai Lu
, (Fri Aug 29, 3:32 pm)
Re: [PATCH] dyn_array: using %pF instead of print_fn_descr ...
, Andrew Morton
, (Fri Aug 29, 3:45 pm)
Re: [PATCH] dyn_array: using %pF instead of print_fn_descr ...
, Andrew Morton
, (Fri Aug 29, 3:53 pm)
Re: [PATCH] dyn_array: using %pF instead of print_fn_descr ...
, Yinghai Lu
, (Fri Aug 29, 4:34 pm)
Re: [PATCH] dyn_array: using %pF instead of print_fn_descr ...
, Andrew Morton
, (Fri Aug 29, 5:23 pm)
Re: [PATCH] dyn_array: using %pF instead of print_fn_descr ...
, Ingo Molnar
, (Sat Sep 6, 10:09 am)
Re: [PATCH] dyn_array: using %pF instead of print_fn_descr ...
, Yinghai Lu
, (Sat Sep 6, 10:16 am)
Re: [PATCH] dyn_array: using %pF instead of print_fn_descr ...
, Ingo Molnar
, (Sat Sep 6, 10:18 am)
Re: [PATCH] dyn_array: using %pF instead of print_fn_descr ...
, Yinghai Lu
, (Sat Sep 6, 10:27 am)
Navigation
Mailing list archives
Recent posts
Popular discussions
linux-kernel
:
Greg Kroah-Hartman
[PATCH 041/196] kobject: add kobject_init_and_add function
Lukas Hejtmanek
Re: Another libata error related to OCZ SSD
Greg Kroah-Hartman
[PATCH 023/196] MCP_UCB1200: Convert from class_device to device
Florian Fainelli
Re: System clock runs too fast after 2.6.27 -> 2.6.28.1 upgrade
Christoph Lameter
[patch 1/4] mmu_notifier: Core code
git
:
Johannes Schindelin
Re: [PATCH 1/2] Add strbuf_initf()
John Bito
[EGIT] Push to GitHub caused corruption
Jakub Narebski
Re: [PATCH 0/2] gitweb: patch view
Junio C Hamano
Re: [PATCH] When a remote is added but not fetched, tell the user.
Andy Parkins
Re: [RFC] Submodules in GIT
git-commits-head
:
Linux Kernel Mailing List
ahci: Workaround HW bug for SB600/700 SATA controller PMP support
Linux Kernel Mailing List
V4L/DVB (11086): au0828: rename macro for currently non-function VBI support
Linux Kernel Mailing List
ceph: client types
Linux Kernel Mailing List
ceph: on-wire types
Linux Kernel Mailing List
crypto: chainiv - Use kcrypto_wq instead of keventd_wq
linux-netdev
:
Andrew Morton
Re: [Bugme-new] [Bug 14969] New: b44: WOL does not work in suspended state
Giuseppe CAVALLARO
Re: [PATCH 03/13] stmmac: add the new Header file for stmmac platform data
Taku Izumi
[PATCH 3/3] ixgbe: add registers etc. printout code just before resetting adapters
Eric Dumazet
rps: some comments
Thomas Gleixner
Re: [RFC PATCH 02/12] On Tue, 23 Sep 2008, David Miller wrote:
openbsd-misc
:
Stephan Andreas
problems with login after xlock in OpenBSD release 4.7
pmc
Make A Change. Alcoholism and Drug Addiction Treatment
ropers
Re: what exactly is enc0?
Fuad NAHDI
Re: What does your environment look like?
Matthew Szudzik
Typo on OpenBSD 4.4 CD Set
Colocation donated by:
Syndicate