From: Philip Li <philip.li@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: kernel test robot <lkp@intel.com>, <oe-kbuild-all@lists.linux.dev>
Subject: Re: [rostedt-trace:pmem-on-reserve-mem-fail 2/10] kernel/trace/ring_buffer.c:1943:34: warning: variable 'bmeta' set but not used
Date: Thu, 13 Feb 2025 11:05:04 +0800 [thread overview]
Message-ID: <Z61hYOLmsekGHJfk@rli9-mobl> (raw)
In-Reply-To: <20250211195421.69854975@gandalf.local.home>
On Tue, Feb 11, 2025 at 07:54:21PM -0500, Steven Rostedt wrote:
>
> Hi,
>
> I sometimes push WIP changes up to my repo to share with others that have
> known issues in it. This branch being one of them. Is there any keyword
> that I can add to the branch to make the kernel test robot not waste CPU
> cycles on testing it?
>
> Like: notest-my-wip-branch
>
> or something?
Thanks Steve, by default, if the branch is named like below, it will be
ignored.
.*experimental.*
.*dont-build
If you prefer any customized branch name or pattern, you can also share
with us, e.g. ".*-wip". We can configure the bot per your needs.
Thanks
>
> Thanks,
>
> -- Steve
>
>
> On Wed, 12 Feb 2025 08:48:01 +0800
> kernel test robot <lkp@intel.com> wrote:
>
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git pmem-on-reserve-mem-fail
> > head: d877ee1b587be39c141df16a6f92efb0e90b30fd
> > commit: 04e1e84239466de5fe5310ddc8899b8b404a5ccc [2/10] ring-buffer: Add buffer meta data for persistent ring buffer
> > config: i386-buildonly-randconfig-002-20250212 (https://download.01.org/0day-ci/archive/20250212/202502120851.VulVvSyg-lkp@intel.com/config)
> > compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250212/202502120851.VulVvSyg-lkp@intel.com/reproduce)
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202502120851.VulVvSyg-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>):
> >
> > kernel/trace/ring_buffer.c: In function 'rb_range_meta_init':
> > >> kernel/trace/ring_buffer.c:1943:34: warning: variable 'bmeta' set but not used [-Wunused-but-set-variable]
> > 1943 | struct ring_buffer_meta *bmeta;
> > | ^~~~~
> >
>
next prev parent reply other threads:[~2025-02-13 3:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 0:48 [rostedt-trace:pmem-on-reserve-mem-fail 2/10] kernel/trace/ring_buffer.c:1943:34: warning: variable 'bmeta' set but not used kernel test robot
2025-02-12 0:54 ` Steven Rostedt
2025-02-13 3:05 ` Philip Li [this message]
2025-02-13 16:42 ` Steven Rostedt
2025-02-14 3:24 ` Philip Li
2025-02-17 16:14 ` Steven Rostedt
2025-02-18 0:33 ` 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=Z61hYOLmsekGHJfk@rli9-mobl \
--to=philip.li@intel.com \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.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.