From: Sami Tolvanen <samitolvanen@google.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: Petr Pavlu <petr.pavlu@suse.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
Luis Chamberlain <mcgrof@kernel.org>,
Daniel Gomez <da.gomez@kernel.org>,
Aaron Tomlin <atomlin@atomlin.com>,
Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH v2] module.lds,codetag: force 0 sh_addr for sections
Date: Tue, 17 Mar 2026 23:10:24 +0000 [thread overview]
Message-ID: <20260317231024.GA2507155@google.com> (raw)
In-Reply-To: <jl7b2iy44nakt6qiyytncemcym22aoddrjixblxcrfgjnnfc3k@vpmf2yfnrokr>
On Tue, Mar 17, 2026 at 03:55:57PM -0700, Josh Poimboeuf wrote:
> On Mon, Mar 16, 2026 at 03:23:20PM +0100, Petr Pavlu wrote:
> > Nonetheless, this can be done separately. I think fixes for these files
> > should better go through architecture-specific trees anyway.
> >
> > I can check the individual architectures and prepare the necessary
> > patches, unless someone else is already looking into this or wants to
> > take a look.
>
> I agree those can be done separately. In the meantime do you plan to
> take this patch in the module tree?
Yes, that's the plan.
Sami
next prev parent reply other threads:[~2026-03-17 23:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 1:52 [PATCH v2] module.lds,codetag: force 0 sh_addr for sections Joe Lawrence
2026-03-05 19:55 ` Josh Poimboeuf
2026-03-06 8:15 ` Petr Pavlu
2026-03-11 21:12 ` Sami Tolvanen
2026-03-12 21:02 ` Joe Lawrence
2026-03-16 14:23 ` Petr Pavlu
2026-03-17 22:55 ` Josh Poimboeuf
2026-03-17 23:10 ` Sami Tolvanen [this message]
2026-03-20 17:45 ` Sami Tolvanen
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=20260317231024.GA2507155@google.com \
--to=samitolvanen@google.com \
--cc=atomlin@atomlin.com \
--cc=da.gomez@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=pmladek@suse.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.