From: Fengguang Wu <lkp@intel.com>
To: Dexuan Cui <decui@microsoft.com>
Cc: Michal Kubecek <mkubecek@suse.cz>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"jasowang@redhat.com" <jasowang@redhat.com>,
Dave Scott <dave.scott@docker.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"joe@perches.com" <joe@perches.com>,
Rolf Neugebauer <rolf.neugebauer@docker.com>,
"kbuild-all@01.org" <kbuild-all@01.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"apw@canonical.com" <apw@canonical.com>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
KY Srinivasan <kys@microsoft.com>,
Cathy Avery <cavery@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [kbuild-all] [PATCH v17 net-next 1/1] hv_sock: introduce Hyper-V Sockets
Date: Wed, 20 Jul 2016 09:52:11 +0800 [thread overview]
Message-ID: <20160720015211.GA20015@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <CO2PR03MB218232E102F17C0E8B3B7764BF080@CO2PR03MB2182.namprd03.prod.outlook.com>
Yes, sorry for the noises!
>> >> net/hv_sock/af_hvsock.o: warning: objtool: hvsock_on_channel_cb()+0x1d:
>> function has unreachable instruction
>
>These warnings are all false alarms.
>
>Thanks,
>-- Dexuan
>_______________________________________________
>kbuild-all mailing list
>kbuild-all@lists.01.org
>https://lists.01.org/mailman/listinfo/kbuild-all
next prev parent reply other threads:[~2016-07-20 1:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 14:32 Dexuan Cui
2016-07-19 17:10 ` kbuild test robot
2016-07-20 1:48 ` Dexuan Cui
2016-07-20 1:52 ` Fengguang Wu [this message]
2016-07-20 2:52 ` David Miller
2016-07-20 3:06 ` [kbuild-all] " Fengguang Wu
2016-07-20 4:05 ` Dexuan Cui
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=20160720015211.GA20015@wfg-t540p.sh.intel.com \
--to=lkp@intel.com \
--cc=apw@canonical.com \
--cc=cavery@redhat.com \
--cc=dave.scott@docker.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=joe@perches.com \
--cc=kbuild-all@01.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=rolf.neugebauer@docker.com \
--cc=vkuznets@redhat.com \
/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®