Re: [PATCH v7 3/4] gicv2m: Refactor to prepare for ACPI support

[Suravee Suthikulanit]

Hi Bjorn,

Thanks for your review. Please see my comments below.

On 12/16/2015 4:12 PM, Bjorn Helgaas wrote:
> On Thu, Dec 10, 2015 at 08:55:29AM -0800, Suravee Suthikulpanit wrote:
> > This patch replaces the struct device_node with struct fwnode_handle
> > since this structure is common between DT and ACPI.
> >
> > It also refactors gicv2m_init_one() to prepare for ACPI support.
> > The only functional change is removing the node name from pr_info.
> >
> > Reviewed-by: Marc Zyngier <marc.zyngier@xxxxxxx>
> > Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@xxxxxxx>
>
> > @@ -359,10 +355,10 @@ static int __init gicv2m_init_one(struct device_node *node,
> >   	}
> >
> >   	list_add_tail(&v2m->entry, &v2m_nodes);
> > -	pr_info("Node %s: range[%#lx:%#lx], SPI[%d:%d]\n", node->name,
> > -		(unsigned long)v2m->res.start, (unsigned long)v2m->res.end,
> > -		v2m->spi_start, (v2m->spi_start + v2m->nr_spis));
> >
> > +	pr_info("range[%#lx:%#lx], SPI[%d:%d]\n",
> > +		(unsigned long)res->start, (unsigned long)res->end,
> > +		v2m->spi_start, (v2m->spi_start + v2m->nr_spis));
>
> You didn't change this, but I don't think this message has enough
> context.  It's pretty cryptic all by itself.  It'd be nice if it could
> at least include a device name, e.g., if you could use dev_info().

Here is the example of the information printed:
[    0.000000] GICv2m: range[0xe1180000:0xe1181000], SPI[64:320]

Basically, the v2m is just an extension of the GIC. Here, we are 
printing the memory range that it is covering, which can be used to 
identify different V2m frame and the associate interrupt range (SPI). 
The node name is not really providing any values. So, we are removing it.

Thanks,
Suravee

> If that's possible, I guess a separate patch would be appropriate,
> since there are other similar things in this file.
> j
> Bjorn



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/