From: Arvid Norlander <lkml@vorpal.se> To: kernel test robot <lkp@intel.com>, platform-driver-x86@vger.kernel.org, linux-pm@vger.kernel.org Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org, Sebastian Reichel <sre@kernel.org>, Hans de Goede <hdegoede@redhat.com>, Azael Avalos <coproscefalo@gmail.com> Subject: Re: [PATCH 2/3] platform/x86: Battery charge mode in toshiba_acpi (sysfs) Date: Mon, 29 Aug 2022 00:44:57 +0200 [thread overview] Message-ID: <90ae872b-9da6-f5a9-56e0-5a61fe3b84ed@vorpal.se> (raw) In-Reply-To: <202208290605.gE9IGbxE-lkp@intel.com> Hi, On 2022-08-29 00:15, kernel test robot wrote: > Hi Arvid, > > Thank you for the patch! Perhaps something to improve: > > [auto build test WARNING on 1c23f9e627a7b412978b4e852793c5e3c3efc555] <snip> > vim +/status +2992 drivers/platform/x86/toshiba_acpi.c > > 2984 > 2985 > 2986 /* ACPI battery hooking */ > 2987 static ssize_t charge_control_end_threshold_show(struct device *device, > 2988 struct device_attribute *attr, > 2989 char *buf) > 2990 { > 2991 int state; >> 2992 int status; Will be fixed in the next version, it should be used. Waiting for human feedback too first. It would be nice to see these warnings locally, anyone know how to turn them on? > 2993 > 2994 if (toshiba_acpi == NULL) { > 2995 pr_err("Toshiba ACPI object invalid\n"); > 2996 return -ENODEV; > 2997 } > 2998 > 2999 status = toshiba_battery_charge_mode_get(toshiba_acpi, &state); > 3000 if (state == 1) > 3001 return sprintf(buf, "80\n"); > 3002 else > 3003 return sprintf(buf, "100\n"); > 3004 } > 3005 > Best regards, Arvid Norlander
WARNING: multiple messages have this Message-ID (diff)
From: Arvid Norlander <lkml@vorpal.se> To: kbuild-all@lists.01.org Subject: Re: [PATCH 2/3] platform/x86: Battery charge mode in toshiba_acpi (sysfs) Date: Mon, 29 Aug 2022 00:44:57 +0200 [thread overview] Message-ID: <90ae872b-9da6-f5a9-56e0-5a61fe3b84ed@vorpal.se> (raw) In-Reply-To: <202208290605.gE9IGbxE-lkp@intel.com> [-- Attachment #1: Type: text/plain, Size: 1149 bytes --] Hi, On 2022-08-29 00:15, kernel test robot wrote: > Hi Arvid, > > Thank you for the patch! Perhaps something to improve: > > [auto build test WARNING on 1c23f9e627a7b412978b4e852793c5e3c3efc555] <snip> > vim +/status +2992 drivers/platform/x86/toshiba_acpi.c > > 2984 > 2985 > 2986 /* ACPI battery hooking */ > 2987 static ssize_t charge_control_end_threshold_show(struct device *device, > 2988 struct device_attribute *attr, > 2989 char *buf) > 2990 { > 2991 int state; >> 2992 int status; Will be fixed in the next version, it should be used. Waiting for human feedback too first. It would be nice to see these warnings locally, anyone know how to turn them on? > 2993 > 2994 if (toshiba_acpi == NULL) { > 2995 pr_err("Toshiba ACPI object invalid\n"); > 2996 return -ENODEV; > 2997 } > 2998 > 2999 status = toshiba_battery_charge_mode_get(toshiba_acpi, &state); > 3000 if (state == 1) > 3001 return sprintf(buf, "80\n"); > 3002 else > 3003 return sprintf(buf, "100\n"); > 3004 } > 3005 > Best regards, Arvid Norlander
next prev parent reply other threads:[~2022-08-28 22:50 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-28 19:29 [PATCH 0/3] platform/x86: Battery charge mode in toshiba_acpi Arvid Norlander 2022-08-28 19:29 ` [PATCH 1/3] platform/x86: Battery charge mode in toshiba_acpi (internals) Arvid Norlander 2022-08-28 19:29 ` [PATCH 2/3] platform/x86: Battery charge mode in toshiba_acpi (sysfs) Arvid Norlander 2022-08-28 22:15 ` kernel test robot 2022-08-28 22:44 ` Arvid Norlander [this message] 2022-08-28 22:44 ` Arvid Norlander 2022-08-29 8:16 ` Miguel Ojeda 2022-08-29 8:16 ` Miguel Ojeda 2022-08-29 16:59 ` Nick Desaulniers 2022-08-29 16:59 ` Nick Desaulniers 2022-08-28 22:36 ` kernel test robot 2022-08-28 19:29 ` [PATCH 3/3] docs: ABI: charge_control_end_threshold may not support all values Arvid Norlander 2022-09-01 21:14 ` Sebastian Reichel 2022-09-01 15:27 ` [PATCH 0/3] platform/x86: Battery charge mode in toshiba_acpi Hans de Goede
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=90ae872b-9da6-f5a9-56e0-5a61fe3b84ed@vorpal.se \ --to=lkml@vorpal.se \ --cc=coproscefalo@gmail.com \ --cc=hdegoede@redhat.com \ --cc=kbuild-all@lists.01.org \ --cc=linux-pm@vger.kernel.org \ --cc=lkp@intel.com \ --cc=llvm@lists.linux.dev \ --cc=platform-driver-x86@vger.kernel.org \ --cc=sre@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.