On 18/06/18 05:06 PM, Andy Shevchenko wrote:
> On Tue, Jun 19, 2018 at 12:44 AM, Alex Williamson
>> There's probably really no path to resolve these, but acknowledging the
>> difference in this comment block might be helpful in the future.
>
> ...or introduce a parser part to allow user supply "any" instead of
> numeric value.
I think the main difficulty is maintaining backwards compatibility. If
anyone is already using zero as a parameter then we will break their system.
>>> + pr_info("PCI: Can't parse resource_alignment parameter: pci:%s\n",
>
>> The "pci:" prefix on %s doesn't make sense now, it was used above when
>> the pointer was already advanced past this token, now I believe it would
>> lead to "pci:pci:xxxx:yyyy" or "pci:xx:yy.z". Thanks,
>
> I'm just wondering if we can use pci_info() here, Or it makes no sense?
> Also, the original loglevel was an "error".
Yeah, I don't think pci_info() makes sense as it's not attached to a
specific device.
Not sure how I messed up the log level, but I'll fix it for v4.
Thanks,
Logan
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
