From: SeongJae Park <sj@kernel.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: SeongJae Park <sj@kernel.org>, 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: Wed, 6 Aug 2025 22:43:49 -0700 [thread overview]
Message-ID: <20250807054349.21561-1-sj@kernel.org> (raw)
In-Reply-To: <81fedf44-83dd-4f2b-9a2b-2f3d7ba4f922@lucifer.local>
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.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2025-08-07 5:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 4:03 [sj:mm-new 42/45] ERROR: modpost: __ex_table+0x1584 references non-executable section '.rodata.spk_ttyio_synth_probe.str1.4' kernel test robot
2025-08-07 5:31 ` Lorenzo Stoakes
2025-08-07 5:43 ` SeongJae Park [this message]
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
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=20250807054349.21561-1-sj@kernel.org \
--to=sj@kernel.org \
--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=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 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.