From: Philip Li <philip.li@intel.com>
To: SeongJae Park <sj@kernel.org>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
kernel test robot <lkp@intel.com>,
Suren Baghdasaryan <surenb@google.com>,
<oe-kbuild-all@lists.linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [sj:mm-new 42/45] ERROR: modpost: __ex_table+0x1584 references non-executable section '.rodata.spk_ttyio_synth_probe.str1.4'
Date: Fri, 8 Aug 2025 14:10:49 +0800 [thread overview]
Message-ID: <aJWU6RA+t1XpJLY/@rli9-mobl> (raw)
In-Reply-To: <20250807155805.25652-1-sj@kernel.org>
On Thu, Aug 07, 2025 at 08:58:05AM -0700, SeongJae Park wrote:
> On Thu, 7 Aug 2025 15:16:46 +0800 Philip Li <philip.li@intel.com> wrote:
>
> > On Wed, Aug 06, 2025 at 10:51:38PM -0700, SeongJae Park wrote:
> > > On Wed, 6 Aug 2025 22:43:49 -0700 SeongJae Park <sj@kernel.org> wrote:
> > >
> > > > On Thu, 7 Aug 2025 06:31:25 +0100 Lorenzo Stoakes <lorenzo.stoakes@oracle.com> wrote:
> > > >
> > > > > +cc SJ, as his tree :)
> > > >
> > > > Thank you, Lorenzo!
> > > >
> > > > >
> > > > > On Thu, Aug 07, 2025 at 12:03:03PM +0800, kernel test robot wrote:
> > > > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git mm-new
> > > > >
> > > > > Not sure why SJ isn't cc'd when it's his tree?
> > > > >
> > > > > Not sure how easy it would be for the scripts to figure this out.
> > > >
> > > > As people might already realized, it is Andrew's mm-new branch. I started
> > > > pushing Andrew's mm-{new,unstable,stable} branches to my tree for backup
> > > > purpose, since DAMON development branch (damon/next) is using mm-new as its
> > > > baseline. Seems it caused confusion to kernel test robot and other people.
> > > > Sorry about that.
> > > >
> > > > kernel test robot, is there a way to mark mm-{new,unstable,stable} branches on
> > > > my tree be ignored from your tests? If there is no good way, I can remove the
> > > > branches from my tree.
> > >
> > > To stop more confusion first rather than waiting for the answer, I just deleted
> > > the mm-{new,unstable,stable} branches from my tree. I don't really depend on
> > > those branches on my tree since I can keep fetching Andrew's tree or using my
> > > trees outside of kernel.org. So this is no problem for me.
> > >
> > > kernel test robot, please let me know if there is a way to mark specific
> > > branches on my tree be ignored from your tests, though, if you get a time and
> > > have an idea.
> >
> > Yes, the test bot supports this to ignore branches by pattern, for example,
> >
> > branch_denylist: .*-wip|.*-v[0-9]*|.*-[0-9]*
> > branch_denylist: mirror/.*
>
> Cool.
>
> >
> > Do you want to just ignore mm-{new,unstable,stable} branches, I can configure the
> > repo to handle this?
>
> Great, could you please do so?
Got it, this is configured now.
>
>
> Thanks,
> SJ
>
> [...]
next prev parent reply other threads:[~2025-08-08 6:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 4:03 kernel test robot
2025-08-07 5:31 ` Lorenzo Stoakes
2025-08-07 5:43 ` SeongJae Park
2025-08-07 5:51 ` SeongJae Park
2025-08-07 7:16 ` Philip Li
2025-08-07 15:58 ` SeongJae Park
2025-08-08 6:10 ` Philip Li [this message]
2025-08-08 17:11 ` SeongJae Park
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=aJWU6RA+t1XpJLY/@rli9-mobl \
--to=philip.li@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sj@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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