> > /*
> > * Certain keys are flagged as KE_IGNORE. All of these are either
> > * notifications (rather than requests for change) or are also sent
> > @@ -513,6 +533,7 @@ static int __init dell_wmi_init(void)
> > {
> > int err;
> > acpi_status status;
> > + struct calling_interface_buffer *buffer;
>
> Please place the longest line first, and move int err to the last declaration.
> When changing declarations of local variables, please use "Reverse Christmas
> Tree" order (longest line to shortest line) wherever possible.
Thanks, I'll keep that in mind for the future, though putting the
WMI-enabling SMBIOS request in a separate function renders the need for
the buffer variable in dell_wmi_init() void, so v4 won't touch this area
any more.
> Pali's point about documenting the hardcoded values and eliminating the code
> duplication with a function (inline) is a good one.
I plan to only put a comment next to 0x51534554 as 0x10000 is apparently
just something pulled out of a hat (as the link provided in the commit
message proves) and input[3] should be self-explanatory due to the name
of the variable whose value is put into it.
By the way, is there any kernel-wide or subsystem-wide policy for
marking a function inline? I mean, this is hardly time-critical code,
so is your suggestion to make it inline just a preference or am I
unaware of some rule?
> Otherwise, this series looks good to me. Looking forward to merging v4.
I'll try to post a v4 within the next couple of days.
--
Best regards,
Michał Kępień
--
To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
