X86 platform drivers
 help / color / mirror / Atom feed
From: Ivan Vecera <ivecera@redhat.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: platform-driver-x86@vger.kernel.org, vadimp@mellanox.com
Subject: Re: [PATCH] platform/x86: mlx-platform: fix module aliases
Date: Mon, 22 Jan 2018 11:12:18 +0100	[thread overview]
Message-ID: <29e4c1ec-ee68-497d-bbac-e6354586bc26@redhat.com> (raw)
In-Reply-To: <87bmhq9g9b.fsf@miraculix.mork.no>

On 19.1.2018 13:37, Bjørn Mork wrote:
> Ivan Vecera <ivecera@redhat.com> writes:
> 
>> Missing prefix 'pn' in MODULE_ALIAS lines causes that the module is
>> not loaded automatically. The patch changes them so they match
>> the entries in mlxplat_dmi_table where BOARD_VENDOR and PRODUCT_NAME
>> are used.
>>
>> Fixes: 6613d18e9038 ("platform/x86: mlx-platform: Move module from arch/x86")
>> Cc: Vadim Pasternak <vadimp@mellanox.com>
>> Signed-off-by: Ivan Vecera <ivecera@redhat.com>
>> ---
>>  drivers/platform/x86/mlx-platform.c | 10 +++++-----
>>  1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/platform/x86/mlx-platform.c b/drivers/platform/x86/mlx-platform.c
>> index 504256c3660d..b1a5bbe4acf0 100644
>> --- a/drivers/platform/x86/mlx-platform.c
>> +++ b/drivers/platform/x86/mlx-platform.c
>> @@ -370,8 +370,8 @@ module_exit(mlxplat_exit);
>>  MODULE_AUTHOR("Vadim Pasternak (vadimp@mellanox.com)");
>>  MODULE_DESCRIPTION("Mellanox platform driver");
>>  MODULE_LICENSE("Dual BSD/GPL");
>> -MODULE_ALIAS("dmi:*:*Mellanox*:MSN24*:");
>> -MODULE_ALIAS("dmi:*:*Mellanox*:MSN27*:");
>> -MODULE_ALIAS("dmi:*:*Mellanox*:MSB*:");
>> -MODULE_ALIAS("dmi:*:*Mellanox*:MSX*:");
>> -MODULE_ALIAS("dmi:*:*Mellanox*:MSN21*:");
>> +MODULE_ALIAS("dmi:*:pnMSN24*:*:rvnMellanoxTechnologies*:");
>> +MODULE_ALIAS("dmi:*:pnMSN27*:*:rvnMellanoxTechnologies*:");
>> +MODULE_ALIAS("dmi:*:pnMSB*:*:rvnMellanoxTechnologies*:");
>> +MODULE_ALIAS("dmi:*:pnMSX*:*:rvnMellanoxTechnologies*:");
>> +MODULE_ALIAS("dmi:*:pnMSN21*:*:rvnMellanoxTechnologies*:");
> 
> Strange.  Why do so many dmi drivers depend on such long and fragile
> lists of aliases instead of simply using
> 
>  MODULE_DEVICE_TABLE(dmi, ..);
> 
> like most other drivers do?  Is there something wrong with file2alias?
> If so, then I believe it would be better to fix that instead.
> 
> 
> Bjørn
> 
Good note, will re-send.

Ivan

      reply	other threads:[~2018-01-22 10:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19  8:31 [PATCH] platform/x86: mlx-platform: fix module aliases Ivan Vecera
2018-01-19 12:37 ` Bjørn Mork
2018-01-22 10:12   ` Ivan Vecera [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=29e4c1ec-ee68-497d-bbac-e6354586bc26@redhat.com \
    --to=ivecera@redhat.com \
    --cc=bjorn@mork.no \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=vadimp@mellanox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox