From: Philip Li <philip.li@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [ti:ti-linux-5.4.y 1/1] net/hsr/hsr_forward.c:244:3: warning: ignoring return value of function declared with 'warn_unused_result' attribute
Date: Mon, 12 Oct 2020 20:12:04 +0800 [thread overview]
Message-ID: <20201012121204.GC23489@intel.com> (raw)
In-Reply-To: <20201012120818.GB23489@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
On Mon, Oct 12, 2020 at 08:08:18PM +0800, Philip Li wrote:
> On Mon, Oct 12, 2020 at 06:42:21AM -0500, Dan Murphy wrote:
> > Hello robot
> >
> > On 10/10/20 2:07 AM, kernel test robot wrote:
> > > tree: git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git ti-linux-5.4.y
> >
> > Why is this TI tree being reported to the open source community? They have
> hi Dan, thanks for the info, this is added automatically, we will
> disable the test of this repo. Sorry for any confusion.
oops, I understand the question wrongly. We will keep testing this repo.
The problem here is it is a clang build, and we currently cc clang mailing list
in case there's doublt that this may be a clang prolem instead of kernel. It
is not specially to whole opoen source community. Is this ok with you?
Thanks
>
> > no interest in our product tree unless this same bug is in the mainline or
> > Linux stable
> >
> > Dan
> >
> > _______________________________________________
> > kbuild-all mailing list -- kbuild-all(a)lists.01.org
> > To unsubscribe send an email to kbuild-all-leave(a)lists.01.org
next prev parent reply other threads:[~2020-10-12 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 7:07 [ti:ti-linux-5.4.y 1/1] net/hsr/hsr_forward.c:244:3: warning: ignoring return value of function declared with 'warn_unused_result' attribute kernel test robot
2020-10-12 11:42 ` Dan Murphy
2020-10-12 12:08 ` Philip Li
2020-10-12 12:12 ` Philip Li [this message]
2020-10-12 12:17 ` Dan Murphy
2020-10-12 12:18 ` Philip Li
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=20201012121204.GC23489@intel.com \
--to=philip.li@intel.com \
--cc=kbuild-all@lists.01.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 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.