public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rong Chen <rong.a.chen@intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
	kernel test robot <lkp@intel.com>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
	kbuild-all@lists.01.org,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Henrique de Moraes Holschuh" <ibm-acpi@hmh.eng.br>,
	"Darren Hart" <dvhart@infradead.org>,
	"Thinkpad-acpi devel ML" <ibm-acpi-devel@lists.sourceforge.net>,
	"Platform Driver" <platform-driver-x86@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [kbuild-all] Re: [RFC PATCH linux-next] platform/x86: thinkpad_acpi: dev_attr_charge_start_threshold can be static
Date: Mon, 3 Aug 2020 08:23:00 +0800	[thread overview]
Message-ID: <095dca8b-e54c-1b5b-4b40-ff3ce43d377e@intel.com> (raw)
In-Reply-To: <CAHp75VcCa4whJ7ry9uU+14suLbGPvKgRFJku3dC+dPVNzc0d5Q@mail.gmail.com>



On 8/1/20 7:45 PM, Andy Shevchenko wrote:
> On Sat, Aug 1, 2020 at 11:38 AM kernel test robot <lkp@intel.com> wrote:
>
> Thanks and sorry folks, Hulk robot was faster, and TBH their patch
> looks much better (proper commit message applied). Perhaps something
> LKP should work on?

Hi Andy,

Thanks for the advice, we'll improve the commit message.

Best Regards,
Rong Chen

>
>> Fixes: e33929537b76 ("platform/x86: thinkpad_acpi: use standard charge control attribute names")
>> Signed-off-by: kernel test robot <lkp@intel.com>
>


      reply	other threads:[~2020-08-03  0:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-01  8:36 [linux-next:master 11232/13260] drivers/platform/x86/thinkpad_acpi.c:9636:25: sparse: sparse: symbol 'dev_attr_charge_start_threshold' was not declared. Should it be kernel test robot
2020-08-01  8:36 ` [RFC PATCH linux-next] platform/x86: thinkpad_acpi: dev_attr_charge_start_threshold can be static kernel test robot
2020-08-01 11:45   ` Andy Shevchenko
2020-08-03  0:23     ` Rong Chen [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=095dca8b-e54c-1b5b-4b40-ff3ce43d377e@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=dvhart@infradead.org \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --cc=ibm-acpi@hmh.eng.br \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=lkp@intel.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