From: "Arnd Bergmann" <arnd@arndb.de>
To: "Suzuki K Poulose" <suzuki.poulose@arm.com>,
"Arnd Bergmann" <arnd@kernel.org>,
"Mathieu Poirier" <mathieu.poirier@linaro.org>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Tao Zhang" <quic_taozha@quicinc.com>,
"Mao Jinlong" <quic_jinlmao@quicinc.com>
Cc: "Mike Leach" <mike.leach@linaro.org>,
"Leo Yan" <leo.yan@linaro.org>,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Coresight: tpda/tpdm: remove incorrect __exit annotation
Date: Thu, 26 Jan 2023 21:37:29 +0100 [thread overview]
Message-ID: <cd4f23d7-cdd7-49e1-8eff-9ec04dcb36c8@app.fastmail.com> (raw)
In-Reply-To: <7ec6bd88-7f18-7eca-fa92-cfea9a25a395@arm.com>
On Thu, Jan 26, 2023, at 19:02, Suzuki K Poulose wrote:
> On 26/01/2023 16:35, Arnd Bergmann wrote:
>> From: Arnd Bergmann <arnd@arndb.de>
> Thanks for the fix, I will queue this. Btw, I did try to
> reproduce it locally, but couldn't trigger the warnings,
> even with
>
> CONFIG_WERROR=y
>
> and all CORESIGHT configs builtin. I see other drivers doing the
> same outside coresight too. Just curious to know why is this
> any different. Is it specific to "bus" driver (e.g. AMBA) ?
The warning comes from postprocessing the object file, it's got
nothing to do with the bus type, only with a symbol in .data
referencing a symbol in .init.text. Maybe there are some
config options that keep the section from getting discarded?
Or possibly you only built the files in this directory, but did
not get to the final link?
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-26 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 16:35 [PATCH] Coresight: tpda/tpdm: remove incorrect __exit annotation Arnd Bergmann
2023-01-26 18:02 ` Suzuki K Poulose
2023-01-26 20:37 ` Arnd Bergmann [this message]
2023-01-27 16:46 ` Suzuki K Poulose
2023-01-27 17:00 ` Arnd Bergmann
2023-01-27 17:12 ` Suzuki K Poulose
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=cd4f23d7-cdd7-49e1-8eff-9ec04dcb36c8@app.fastmail.com \
--to=arnd@arndb.de \
--cc=alexander.shishkin@linux.intel.com \
--cc=arnd@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=quic_jinlmao@quicinc.com \
--cc=quic_taozha@quicinc.com \
--cc=suzuki.poulose@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).