From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Martin Rodriguez Reboredo <yakoyoku@gmail.com>
Cc: linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
rust-for-linux@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Yonghong Song <yhs@fb.com>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Neal Gompa <neal@gompa.dev>
Subject: Re: Fwd: [PATCH bpf] scripts: Exclude Rust CUs with pahole
Date: Mon, 9 Jan 2023 12:39:19 -0300 [thread overview]
Message-ID: <Y7w1J489NWFtCD+7@kernel.org> (raw)
In-Reply-To: <0ca4ad02-af27-0d1f-8750-1ff6b34e8d2a@gmail.com>
Em Sat, Jan 07, 2023 at 11:23:11PM -0300, Martin Rodriguez Reboredo escreveu:
> On 1/5/23 13:40, Eric Curtin wrote:
> > Hiya Martin,
> >
> > Just in case you hadn't noticed, the test bot complained about this...
> >
> >>> grep: include/config/auto.conf: No such file or directory
> > --
> >>> grep: include/config/auto.conf: No such file or directory
> >>> grep: include/config/auto.conf: No such file or directory
> >>> grep: include/config/auto.conf: No such file or directory
> >
> > Is mise le meas/Regards,
> >
> > Eric Curtin
> >
> > On Sun, 1 Jan 2023 at 08:57, kernel test robot <lkp@intel.com> wrote:
> >>
> >> Hi Martin,
> >>
> >> Thank you for the patch! Yet something to improve:
> >>
> >> [auto build test ERROR on bpf/master]
> >>
> >> url: https://github.com/intel-lab-lkp/linux/commits/Martin-Rodriguez-Reboredo/scripts-Exclude-Rust-CUs-with-pahole/20221221-112806
> >> base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git master
> >> patch link: https://lore.kernel.org/r/20221220203901.1333304-1-yakoyoku%40gmail.com
> >> patch subject: [PATCH bpf] scripts: Exclude Rust CUs with pahole
> >> config: sh-se7724_defconfig
> >> compiler: sh4-linux-gcc (GCC) 12.1.0
> >> reproduce (this is a W=1 build):
> >> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> >> chmod +x ~/bin/make.cross
> >> # https://github.com/intel-lab-lkp/linux/commit/24aac5fd4ea59e02e9c203d3a59be6f13c5e702f
> >> git remote add linux-review https://github.com/intel-lab-lkp/linux
> >> git fetch --no-tags linux-review Martin-Rodriguez-Reboredo/scripts-Exclude-Rust-CUs-with-pahole/20221221-112806
> >> git checkout 24aac5fd4ea59e02e9c203d3a59be6f13c5e702f
> >> # save the config file
> >> mkdir build_dir && cp config build_dir/.config
> >> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=sh olddefconfig
> >> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=sh distclean
> >>
> >> If you fix the issue, kindly add following tag where applicable
> >> | Reported-by: kernel test robot <lkp@intel.com>
> >>
> >> All errors (new ones prefixed by >>):
> >>
> >>>> grep: include/config/auto.conf: No such file or directory
> >> --
> >>>> grep: include/config/auto.conf: No such file or directory
> >>>> grep: include/config/auto.conf: No such file or directory
> >>>> grep: include/config/auto.conf: No such file or directory
> >>
> >> --
> >> 0-DAY CI Kernel Test Service
> >> https://01.org/lkp
> >
>
> I see, I was making a dependency on `auto.conf` in `pahole-flags.sh` but
> the former gets generated after the latter is called, so that's the
> reason behind the `grep` errors. Sent a new version of the patch.
I'll wait a bit then try to finally get into the rust bandwagon by
actually testing all this to ack this.
- Arnaldo
prev parent reply other threads:[~2023-01-09 15:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <828d438e-afe3-1fc0-bc12-ac98632c0908@gmail.com>
2023-01-08 2:23 ` Fwd: [PATCH bpf] scripts: Exclude Rust CUs with pahole Martin Rodriguez Reboredo
2023-01-09 15:39 ` Arnaldo Carvalho de Melo [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=Y7w1J489NWFtCD+7@kernel.org \
--to=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=neal@gompa.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=yakoyoku@gmail.com \
--cc=yhs@fb.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 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.