lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 11 Sep 2014 10:23:36 +0200 (CEST)
From:	Thomas Gleixner <>
To:	Jiang Liu <>
cc:	Benjamin Herrenschmidt <>,
	Ingo Molnar <>,
	"H. Peter Anvin" <>,
	"Rafael J. Wysocki" <>,
	Bjorn Helgaas <>,
	Randy Dunlap <>,
	Yinghai Lu <>,
	Borislav Petkov <>,
	Grant Likely <>,
	Konrad Rzeszutek Wilk <>,
	Andrew Morton <>,
	Tony Luck <>,
	Joerg Roedel <>,
	Greg Kroah-Hartman <>,,,,
Subject: Re: [Patch v5 04/15] ACPI: Add interfaces to parse IOAPIC ID for
 IOAPIC hotplug

On Thu, 11 Sep 2014, Jiang Liu wrote:
> +
> +static int map_ioapic_id(struct acpi_subtable_header *entry, u32 gsi_base,
> +			 u64 *phys_addr, int *ioapic_id)

I find these function names map_* quite confusing. All they do is a
lookup, right?

> +/**
> + * acpi_get_ioapic_id() - Get IOAPIC ID and physical address matching @gsi_base
> + * @handle ACPI object for IOAPIC device

Proper docbook formatting is:

 * acpi_get_ioapic_id - Get ....
 * @handle:	 ACPI object     


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists