From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>, kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Javier Martinez Canillas <javierm@redhat.com>,
David Herrmann <dh.herrmann@gmail.com>
Subject: Re: [kbuild-all] Re: drivers/firmware/efi/sysfb_efi.c:190:35: warning: unused variable 'efifb_dmi_system_table'
Date: Mon, 17 Jan 2022 09:16:16 +0800 [thread overview]
Message-ID: <3731657b-a4d6-b7e3-007d-76e70a01628a@intel.com> (raw)
In-Reply-To: <f9336852-d741-5483-a6f5-3cd05b233022@infradead.org>
On 1/15/2022 8:06 AM, Randy Dunlap wrote:
> Hi lkp robot,
>
> I have a metaquestion, please:
>
>
> On 1/4/22 03:52, kernel test robot wrote:
>> Hi Randy,
>>
>> FYI, the error/warning still remains.
>>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head: c9e6606c7fe92b50a02ce51dda82586ebdf99b48
>> commit: 15d27b15de965043d6f8e23bc7f34386fcd1a772 efi: sysfb_efi: fix build when EFI is not set
>>
>
> [snip]
>
> Why is the patch committer (David Herrmann) not cc-ed on your original email?
> (I am adding him now.)
>
> bu I have seen this multiple times, where the TO: person (below) is not cc-ed
> on the problem email. I don't understand.
Hi Randy,
The lkp robot sent the report to the people mentioned in the first bad
commit (15d27b15de) from bisection, the below commit (2995e50627) is
from git blame (drivers/firmware/efi/sysfb_efi.c:190), sometimes the
commits are not the same.
Best Regards,
Rong Chen
>
>>
>> :::::: The code at line 190 was first introduced by commit
>> :::::: 2995e506276bfdc7311eb02db8b2aa1a61a4b849 x86: sysfb: move EFI quirks from efifb to sysfb
>>
>> :::::: TO: David Herrmann <dh.herrmann@gmail.com>
>> :::::: CC: H. Peter Anvin <hpa@linux.intel.com>
>>
>> ---
>> 0-DAY CI Kernel Test Service, Intel Corporation
>> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>
> thanks.
>
prev parent reply other threads:[~2022-01-17 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 11:52 kernel test robot
2022-01-15 0:06 ` Randy Dunlap
2022-01-17 1:16 ` 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=3731657b-a4d6-b7e3-007d-76e70a01628a@intel.com \
--to=rong.a.chen@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dh.herrmann@gmail.com \
--cc=javierm@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=rdunlap@infradead.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®