From: "Hegde, Suma" <Suma.Hegde@amd.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: naveenkrishna.chatradhi@amd.com,
LKML <linux-kernel@vger.kernel.org>,
Carlos Bilbao <carlos.bilbao@amd.com>,
Hans de Goede <hdegoede@redhat.com>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] platform/x86/amd/hsmp: switch to use device_add_groups()
Date: Thu, 1 Feb 2024 18:50:33 +0530 [thread overview]
Message-ID: <e73426f6-6d50-4ed7-8613-1ec42fa3f991@amd.com> (raw)
In-Reply-To: <0d110d2a-da0c-017a-0e5a-fc6bef7b066a@linux.intel.com>
On 1/29/2024 6:16 PM, Ilpo Järvinen wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> + Cc Suma Hegde.
>
> On Sun, 28 Jan 2024, Greg Kroah-Hartman wrote:
>
>> The use of devm_*() functions works properly for when the device
>> structure itself is dynamic, but the hsmp driver is attempting to have a
>> local, static, struct device and then calls devm_() functions attaching
>> memory to the device that will never be freed.
>>
>> The logic of having a static struct device is almost never a wise
>> choice, but for now, just remove the use of devm_device_add_groups() in
>> this driver as it obviously is not needed.
Hi Greg,
Could you please hold on merging this patch for a week? I will push a
patch for converting platform specific structure's memory allocation
from static to a dynamic
allocation.
>>
>> Cc: Naveen Krishna Chatradhi <naveenkrishna.chatradhi@amd.com>
>> Cc: Carlos Bilbao <carlos.bilbao@amd.com>
>> Cc: Hans de Goede <hdegoede@redhat.com>
>> Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
>> Cc: platform-driver-x86@vger.kernel.org
>> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> ---
>> drivers/platform/x86/amd/hsmp.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/platform/x86/amd/hsmp.c b/drivers/platform/x86/amd/hsmp.c
>> index b55d80e29139..49ef0b1d6df0 100644
>> --- a/drivers/platform/x86/amd/hsmp.c
>> +++ b/drivers/platform/x86/amd/hsmp.c
>> @@ -471,7 +471,7 @@ static int hsmp_create_sysfs_interface(void)
>> if (ret)
>> return ret;
>> }
>> - return devm_device_add_groups(plat_dev.dev, hsmp_attr_grps);
>> + return device_add_groups(plat_dev.dev, hsmp_attr_grps);
>> }
> Thanks Greg for bringing this up. I've added Suma who has some patches
> which change code around this area.
Thanks Ilpo for adding me. I will push patch to address above issue on
top of "Add ACPI probing support for HSMP" patch series.
> --
> i.
Thanks and Regards,
Suma
next prev parent reply other threads:[~2024-02-01 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 18:56 Greg Kroah-Hartman
2024-01-29 12:46 ` Ilpo Järvinen
2024-02-01 13:20 ` Hegde, Suma [this message]
2024-02-01 14:22 ` Greg Kroah-Hartman
2024-02-01 14:34 ` Ilpo Järvinen
2024-02-01 14:47 ` Greg Kroah-Hartman
2024-02-01 14:50 ` Hans de Goede
2024-02-01 15:34 ` Greg Kroah-Hartman
2024-02-02 10:33 ` Hegde, Suma
2024-02-02 2:40 ` Greg Kroah-Hartman
2024-02-02 2:42 ` Greg Kroah-Hartman
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=e73426f6-6d50-4ed7-8613-1ec42fa3f991@amd.com \
--to=suma.hegde@amd.com \
--cc=carlos.bilbao@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naveenkrishna.chatradhi@amd.com \
--cc=platform-driver-x86@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®