From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: Andrew Morton <akpm@osdl.org>, Len Brown <len.brown@intel.com>,
"Luck, Tony" <tony.luck@intel.com>, Greg KH <greg@kroah.com>,
acpi-devel@lists.sourceforge.net, linux-ia64@vger.kernel.org,
pcihpd-discuss@lists.sourceforge.net
Subject: Re: [ACPI] [RFC/PATCH 2/3] ACPI based I/O APIC hot-plug
Date: Thu, 21 Apr 2005 11:21:53 -0600 [thread overview]
Message-ID: <1114104113.2784.41.camel@eeyore> (raw)
In-Reply-To: <4267AD1B.3040001@jp.fujitsu.com>
> +acpi_status __devinit
> acpi_map_iosapic (acpi_handle handle, u32 depth, void *context, void **ret)
I think "acpi_map_iosapic" is poorly named. It's really associating
an iosapic with a locality domain.
And there's nothing ia64-specific in acpi_map_iosapic(). It'd be
nice to figure out a way to move it into generic ACPI code.
But your patch didn't introduce either of these problems, so
I don't think you have to fix them now.
> unsigned short num_rte; /* number of RTE in this IOSAPIC */
> + int count; /* # of RTEs in use on this IOSAPIC */
"count" isn't very descriptive. Maybe "rtes_inuse" or similar?
> -void __init
> +static inline int iosapic_alloc (void)
Nitpick: should be
static inline int
iosapic_alloc (void)
to match the style of the rest of the file.
> +static inline void free_iosapic (int index)
Nitpick: follow style again.
> + memset(&iosapic_lists[index], 0, sizeof(struct iosapic));
What about
memset(&iosapic_lists[index], 0, sizeof(iosapic_lists[0]));
so you can tell this is correct without looking up the declaration of
iosapic_lists[]?
> +static inline int iosapic_check (unsigned int gsi_base, unsigned int ver)
Nitpick: follow style again. And maybe a more descriptive name?
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: Andrew Morton <akpm@osdl.org>, Len Brown <len.brown@intel.com>,
"Luck, Tony" <tony.luck@intel.com>, Greg KH <greg@kroah.com>,
acpi-devel@lists.sourceforge.net, linux-ia64@vger.kernel.org,
pcihpd-discuss@lists.sourceforge.net
Subject: Re: [ACPI] [RFC/PATCH 2/3] ACPI based I/O APIC hot-plug
Date: Thu, 21 Apr 2005 17:21:53 +0000 [thread overview]
Message-ID: <1114104113.2784.41.camel@eeyore> (raw)
In-Reply-To: <4267AD1B.3040001@jp.fujitsu.com>
> +acpi_status __devinit
> acpi_map_iosapic (acpi_handle handle, u32 depth, void *context, void **ret)
I think "acpi_map_iosapic" is poorly named. It's really associating
an iosapic with a locality domain.
And there's nothing ia64-specific in acpi_map_iosapic(). It'd be
nice to figure out a way to move it into generic ACPI code.
But your patch didn't introduce either of these problems, so
I don't think you have to fix them now.
> unsigned short num_rte; /* number of RTE in this IOSAPIC */
> + int count; /* # of RTEs in use on this IOSAPIC */
"count" isn't very descriptive. Maybe "rtes_inuse" or similar?
> -void __init
> +static inline int iosapic_alloc (void)
Nitpick: should be
static inline int
iosapic_alloc (void)
to match the style of the rest of the file.
> +static inline void free_iosapic (int index)
Nitpick: follow style again.
> + memset(&iosapic_lists[index], 0, sizeof(struct iosapic));
What about
memset(&iosapic_lists[index], 0, sizeof(iosapic_lists[0]));
so you can tell this is correct without looking up the declaration of
iosapic_lists[]?
> +static inline int iosapic_check (unsigned int gsi_base, unsigned int ver)
Nitpick: follow style again. And maybe a more descriptive name?
next prev parent reply other threads:[~2005-04-21 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 13:39 [RFC/PATCH 2/3] ACPI based I/O APIC hot-plug Kenji Kaneshige
2005-04-21 13:39 ` Kenji Kaneshige
2005-04-21 17:21 ` Bjorn Helgaas [this message]
2005-04-21 17:21 ` [ACPI] " Bjorn Helgaas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1114104113.2784.41.camel@eeyore \
--to=bjorn.helgaas@hp.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=len.brown@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.