From: Florian Westphal <fw@strlen.de>
To: kernel test robot <lkp@intel.com>
Cc: Florian Westphal <fw@strlen.de>,
kbuild-all@lists.01.org, netdev@vger.kernel.org,
Steffen Klassert <steffen.klassert@secunet.com>
Subject: Re: [ipsec-next:testing 10/10] net/xfrm/xfrm_output.c:100:33: error: 'nh' undeclared
Date: Fri, 11 Jun 2021 11:44:36 +0200 [thread overview]
Message-ID: <20210611094436.GR20020@breakpoint.cc> (raw)
In-Reply-To: <202106111714.at0vSzPp-lkp@intel.com>
kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git testing
> head: 65b3564d0c98ea3c0ca4f19d5edd9b77090d8998
> commit: 65b3564d0c98ea3c0ca4f19d5edd9b77090d8998 [10/10] xfrm: merge dstopt and routing hdroff functions
> config: sh-randconfig-s031-20210611 (attached as .config)
> compiler: sh4-linux-gcc (GCC) 9.3.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # apt-get install sparse
> # sparse version: v0.6.3-341-g8af24329-dirty
> # https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git/commit/?id=65b3564d0c98ea3c0ca4f19d5edd9b77090d8998
> git remote add ipsec-next https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git
> git fetch --no-tags ipsec-next testing
> git checkout 65b3564d0c98ea3c0ca4f19d5edd9b77090d8998
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=sh
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
Ouch, my bad. I'll send a fix.
prev parent reply other threads:[~2021-06-11 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 9:37 [ipsec-next:testing 10/10] net/xfrm/xfrm_output.c:100:33: error: 'nh' undeclared kernel test robot
2021-06-11 9:44 ` Florian Westphal [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=20210611094436.GR20020@breakpoint.cc \
--to=fw@strlen.de \
--cc=kbuild-all@lists.01.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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;
as well as URLs for NNTP newsgroup(s).