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: Tue, 18 Feb 2025 08:33:59 +0800 [thread overview]
Message-ID: <Z7PVd5941DTfszzr@rli9-mobl> (raw)
In-Reply-To: <20250217111430.243c3560@gandalf.local.home>
On Mon, Feb 17, 2025 at 11:14:30AM -0500, Steven Rostedt wrote:
> On Fri, 14 Feb 2025 11:24:09 +0800
> Philip Li <philip.li@intel.com> wrote:
>
>
> > Got it, thanks for the info, I will remove this repo.
> >
> > BTW: the 0day bot records 2 other repos from your side, do we need keep
> > them or also remove?
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest.git
>
> Although I do use this to send code upstream, you don't need to test this
> repo, because ktest is a user space tool. Unless you are using the ktest
> code (tools/testing/ktest/ktest.pl), there's nothing changing there that
> would affect the kernel.
Thanks for info, currently we don't use this ktest.pl, and we will remove this repo.
>
> > https://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-kconfig.git
>
> This one I would still keep. I use it to modify the build system some
> times, and this can cause regressions in the build of the Linux kernel.
> I seldom modify it though, as I don't touch the build system that often.
Got it, we will continue monitoring this one.
>
> -- Steve
prev parent reply other threads:[~2025-02-18 0:34 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
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 [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=Z7PVd5941DTfszzr@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.