From: "Luke Jones" <luke@ljones.dev>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org, corentin.chary@gmail.com,
"Hans de Goede" <hdegoede@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
"Denis Benato" <benato.denis96@gmail.com>
Subject: Re: [PATCH] Fixes: ae834a549ec1 ("platform/x86: asus-wmi: add support variant of TUF RGB")
Date: Tue, 16 Jul 2024 13:00:59 +1200 [thread overview]
Message-ID: <18eabcb8-06a6-497a-ac12-c04c9f0db70c@app.fastmail.com> (raw)
In-Reply-To: <5c4ef8d8-2806-5bb6-2946-368cf1ebbac6@linux.intel.com>
On Mon, 15 Jul 2024, at 9:27 PM, Ilpo Järvinen wrote:
> On Sat, 13 Jul 2024, Luke D. Jones wrote:
>
> > In kbd_rgb_mode_store the dev_get_drvdata() call was assuming the device
> > data was asus_wmi when it was actually led_classdev.
> >
> > This patch corrects this by making the correct chain of calls to get the
> > asus_wmi driver data.
> >
> > Tested-by: Denis Benato <benato.denis96@gmail.com>
> > Signed-off-by: Luke D. Jones <luke@ljones.dev>
>
> Your tags seem messed up, Fixes is in Subject in place of shortlog that is
> completely missing.
>
> Could you please correct these issues and resubmit, thank you.
Looks like I misunderstood something somewhere. Will resubmit.
>
> --
> i.
>
> > ---
> > drivers/platform/x86/asus-wmi.c | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/platform/x86/asus-wmi.c b/drivers/platform/x86/asus-wmi.c
> > index 799d928c7d3d..2935af013535 100644
> > --- a/drivers/platform/x86/asus-wmi.c
> > +++ b/drivers/platform/x86/asus-wmi.c
> > @@ -879,10 +879,14 @@ static ssize_t kbd_rgb_mode_store(struct device *dev,
> > struct device_attribute *attr,
> > const char *buf, size_t count)
> > {
> > - struct asus_wmi *asus = dev_get_drvdata(dev);
> > u32 cmd, mode, r, g, b, speed;
> > + struct led_classdev *led;
> > + struct asus_wmi *asus;
> > int err;
> >
> > + led = dev_get_drvdata(dev);
> > + asus = container_of(led, struct asus_wmi, kbd_led);
> > +
> > if (sscanf(buf, "%d %d %d %d %d %d", &cmd, &mode, &r, &g, &b, &speed) != 6)
> > return -EINVAL;
> >
> >
>
prev parent reply other threads:[~2024-07-16 1:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 7:40 Luke D. Jones
2024-07-15 9:27 ` Ilpo Järvinen
2024-07-16 1:00 ` Luke Jones [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=18eabcb8-06a6-497a-ac12-c04c9f0db70c@app.fastmail.com \
--to=luke@ljones.dev \
--cc=benato.denis96@gmail.com \
--cc=corentin.chary@gmail.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--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®