From: Dan Carpenter <dan.carpenter@linaro.org>
To: Ethan Carter Edwards <ethan@ethancedwards.com>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jakub Kicinski <kuba@kernel.org>,
Dan Carpenter <error27@gmail.com>
Subject: Re: [linux-next:master 2357/7423] drivers/bluetooth/hci_vhci.o: warning: objtool: .text: unexpected end of section
Date: Sun, 2 Mar 2025 15:35:01 +0300 [thread overview]
Message-ID: <dc1b62ed-8a86-4424-8a1d-bc20866fb4d9@stanley.mountain> (raw)
In-Reply-To: <5jkf4f2bqmomecoxzzdyhdo2qg7dso2jihzwcox6zufnurrwtm@o5gqbsgmpldy>
On Sat, Mar 01, 2025 at 11:15:46AM -0500, Ethan Carter Edwards wrote:
> On 25/03/01 12:30PM, kernel test robot wrote:
> > Hi Ethan,
> >
> > FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
> >
>
> Thanks for the email, kernel test bot. I'm not sure my patch would be
> the cause of this error, especially since my patch did not touch
> bluetooth at all. Only the ham radio driver.
>
> I did find an email [0] from a year ago with the exact same error in
> the same file.
>
> Dan, what your thoughts?
>
Is this a Clang bug?
I can't imagine what's going on here. I didn't try the reproducer, but I
I downloaded the .config and did a clang19 build and it worked for me. I
wouldn't worry about it.
regards,
dan carpenter
next prev parent reply other threads:[~2025-03-02 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 4:30 [linux-next:master 2357/7423] drivers/bluetooth/hci_vhci.o: warning: objtool: .text: unexpected end of section kernel test robot
2025-03-01 16:15 ` Ethan Carter Edwards
2025-03-02 12:35 ` Dan Carpenter [this message]
2025-03-02 21:10 ` Nathan Chancellor
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=dc1b62ed-8a86-4424-8a1d-bc20866fb4d9@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=error27@gmail.com \
--cc=ethan@ethancedwards.com \
--cc=kuba@kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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