All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Pavel Machek <pavel@ucw.cz>, kernel test robot <lkp@intel.com>,
	kernel list <linux-kernel@vger.kernel.org>
Cc: "Andrew Jeffery" <andrew@aj.id.au>,
	llvm@lists.linux.dev, kbuild-all@lists.01.org,
	"Linux Memory Management List" <linux-mm@kvack.org>,
	"Cédric Le Goater" <clg@kaod.org>
Subject: Re: [kbuild-all] Unsigned emails from Intel robot was Re: [linux-next:master 9122/14381] drivers/leds/leds-pca955x.c:149:19: warning: unused function 'pca95xx_num_led_regs'
Date: Mon, 28 Mar 2022 13:21:54 +0800	[thread overview]
Message-ID: <a244acc9-eff3-e666-d703-1ba63d5a037d@intel.com> (raw)
In-Reply-To: <20220326092537.GA8704@amd>



On 3/26/2022 5:25 PM, Pavel Machek wrote:
> Hey robot!
> 
>> FYI, the error/warning still remains.
> 
> Could you please sign emails with real name of person responsible for
> this? Was there human writing this?

Hi Pavel,

The report was generated automatically, we continue to optimize the bot
to output the right result.

> 
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
> 
> I'd preffer to credit human if human was involved.
> 
>>>> drivers/leds/leds-pca955x.c:149:19: warning: unused function 'pca95xx_num_led_regs'
>>     static inline int pca95xx_num_led_regs(int bits)
>>     ^
>>     fatal error: error in backend: Nested variants found in inline asm string: ' .set push
>>     .set mips64r2
> 
> This sounds like an compiler problem, not a kernel problem, right?

Yes, it's not related to your commit, sorry for the inconvenience,
we'll take a look at it to avoid false positive next time.

Best Regards,
Rong Chen

      reply	other threads:[~2022-03-28  5:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25 22:55 [linux-next:master 9122/14381] drivers/leds/leds-pca955x.c:149:19: warning: unused function 'pca95xx_num_led_regs' kernel test robot
2022-03-26  9:25 ` Unsigned emails from Intel robot was " Pavel Machek
2022-03-26  9:25   ` Pavel Machek
2022-03-28  5:21   ` Chen, Rong A [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=a244acc9-eff3-e666-d703-1ba63d5a037d@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=andrew@aj.id.au \
    --cc=clg@kaod.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=pavel@ucw.cz \
    /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 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.