From: Kai-Chuan Hsieh <kaichuan.hsieh@canonical.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware/dmi: Include product_sku info to modalias
Date: Wed, 28 Oct 2020 17:15:00 +0800 [thread overview]
Message-ID: <c165ab45-dbcc-8d7a-10ad-a66d6a157fbe@canonical.com> (raw)
In-Reply-To: <20201028100455.28cad0f5@endymion>
Hello Jean,
Thanks for your reminder, I'll read the document for future submission.
Sorry for not following the rule this time.
Thanks,
KaiChuan
On 10/28/20 5:04 PM, Jean Delvare wrote:
> Hi Kai-Chuan,
>
> On Wed, 28 Oct 2020 11:50:15 +0800, Kai-Chuan Hsieh wrote:
>> Some Dell platforms rely on modalias to customize configuration,
>> the product sku can be more specific for the hardware.
>>
>> Add product_sku to modalias for better utilization.
>>
>> Signed-off-by: Kai-Chuan Hsieh <kaichuan.hsieh@canonical.com>
>> ---
>> drivers/firmware/dmi-id.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/firmware/dmi-id.c b/drivers/firmware/dmi-id.c
>> index 86d71b0212b1..4d5421d14a41 100644
>> --- a/drivers/firmware/dmi-id.c
>> +++ b/drivers/firmware/dmi-id.c
>> @@ -85,6 +85,7 @@ static ssize_t get_modalias(char *buffer, size_t buffer_size)
>> { "svn", DMI_SYS_VENDOR },
>> { "pn", DMI_PRODUCT_NAME },
>> { "pvr", DMI_PRODUCT_VERSION },
>> + { "sku", DMI_PRODUCT_SKU },
>> { "rvn", DMI_BOARD_VENDOR },
>> { "rn", DMI_BOARD_NAME },
>> { "rvr", DMI_BOARD_VERSION },
>
> Applied, thanks.
>
> For your future submissions, I invite you to read
> Documentation/process/submitting-patches.rst
>
> Specifically, when submitting a new version of a patch, please:
> * Replace [PATCH] with [PATCH v2] in the subject.
> * Do not reply to the previous version of the patch, instead start a
> new thread.
> * Ideally, include a list of changes from previous version, between the
> "---" marker and the diffstat.
>
> Thanks,
>
next prev parent reply other threads:[~2020-10-29 1:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 3:50 Kai-Chuan Hsieh
2020-10-28 9:04 ` Jean Delvare
2020-10-28 9:15 ` Kai-Chuan Hsieh [this message]
[not found] <20201022064936.10854-1-kaichuan.hsieh@canonical.com>
2020-10-28 4:38 ` Kai-Chuan Hsieh
[not found] <[PATCH] firmware/dmi: Include product_sku info to modalias>
2020-10-28 4:13 ` Kai-Chuan Hsieh
-- strict thread matches above, loose matches on Subject: below --
2020-10-22 6:40 kaichuan.hsieh
2020-10-22 12:42 ` Jean Delvare
2020-10-22 13:11 ` Kai-Chuan Hsieh
2020-10-27 16:12 ` Jean Delvare
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=c165ab45-dbcc-8d7a-10ad-a66d6a157fbe@canonical.com \
--to=kaichuan.hsieh@canonical.com \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®