Thread (22 messages) 22 messages, 6 authors, 2018-02-14

Re: [PATCH v12 7/9] ACPI: Translate the I/O range of non-MMIO devices before scanning

From: Andy Shevchenko <hidden>
Date: 2018-02-05 13:16:14
Also in: linux-acpi, linux-arch, linux-pci, lkml

On Thu, Feb 1, 2018 at 1:32 PM, John Garry [off-list ref] wrote:


I'm not going through all patch, by one thing I would like you to pay
attention on, i.e.
printing resource_size_t and struct resource
quoted
+               dev_err(dev, "translate bus-addr(0x%llx) fail!\n",
+                       resource->start);
resource_size_t is dynamic width type, you will see a compiler
warning. For this we have
%pap specifier.

Moreover, in some cases it's useful to print struct resource via %pR or %pr.

Consider reading kernel documentation about these (printk-formats.rst).
quoted
+struct acpi_indirectio_host_data {
+       resource_size_t io_size;
+       resource_size_t io_start;
+};
Why not utilize struct resource?

If it's coming from platform / firmware it should *never* have types
like size_t, unsigned long, resource_size_t, etc.
quoted
+/* All the host devices which apply indirect-IO can be listed here. */
+static const struct acpi_device_id acpi_indirect_host_id[] = {
+       {""},
+};
The idea of terminator is to be such (remove comma there). And it's
basically redundant to have an empty string there. Moreover, it's a
waste of resources in ro section.

-- 
With Best Regards,
Andy Shevchenko
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help