From: Hans de Goede <hdegoede@redhat.com>
To: "Barnabás Pőcze" <pobrn@protonmail.com>
Cc: Mark Gross <mgross@linux.intel.com>, platform-driver-x86@vger.kernel.org
Subject: Re: [RFC PATCH v1 13/30] platform/x86: wmi: use dynamic debug to print data about events
Date: Mon, 13 Sep 2021 12:30:09 +0200 [thread overview]
Message-ID: <8e7cd191-633e-3ef6-4e18-c9207eb8a19e@redhat.com> (raw)
In-Reply-To: <bh-WuyQoOPt-bn0_bhN86zDXoltPaAI1BQ-jNRsDv_MApIiYNNhTQOslgbbiRv2KzcRq_m-N9ZtXvel-qu22r2W6m5UzUgXOLCBHPCENscE=@protonmail.com>
Hi Barnabás,
On 9/13/21 12:09 PM, Barnabás Pőcze wrote:
> Hi
>
>
> 2021. szeptember 13., hétfő 11:43 keltezéssel, Hans de Goede írta:
>>> - if (debug_event)
>>> - pr_info("DEBUG Event GUID: %pUL\n", wblock->gblock.guid);
>>> + dev_dbg(&wblock->dev.dev, "event 0x%02X\n", event);
>>
>> The debug_event value gets set by a module-parameter and several WMI related
>> howto-s and forum threads on the web refer to this. At one point in time even:
>> https://wiki.ubuntu.com/Hotkeys/Troubleshooting
>>
>> Used to refer to this, but they seem to have dropped this.
>>
>> Either way this changes makes users have to also deal with dyndbg stuff to
>> get the same info which before they could get with just the debug_event module
>> param, which makes debugging harder, so I'm going to drop this patch from the
>> series.
>
> Would you consider accepting a patch that changes it to:
>
> if (debug_event)
> dev_info(&wblock->dev.dev, "event 0x%02X\n", event);
>
> ?
So I've just finished reviewing the series and I've pushed it out to
my review-hans branch minus this patch and I've also dropped patch 17 as
you requested.
I've added the "event 0x%02X\n", event bit to the existing pr_info, because I agree
that printing the event is useful.
I've squashed this change into the:
"[RFC PATCH v1 23/30] platform/x86: wmi: improve debug messages"
patch since that was making the same change for the wmi_notify_debug() code.
If you want to send out a follow-up patch/series on top of my current review-hans
switching to dev_info(), then that would be a welcome improvement, but in that
case please replace all pr_info() calls with dev_info(), not just this one.
Regards,
Hans
prev parent reply other threads:[~2021-09-13 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 17:55 [RFC PATCH v1 13/30] platform/x86: wmi: use dynamic debug to print data about events Barnabás Pőcze
2021-09-13 9:43 ` Hans de Goede
2021-09-13 10:09 ` Barnabás Pőcze
2021-09-13 10:30 ` Hans de Goede [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=8e7cd191-633e-3ef6-4e18-c9207eb8a19e@redhat.com \
--to=hdegoede@redhat.com \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pobrn@protonmail.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;
as well as URLs for NNTP newsgroup(s).