From: "wsa-dev@sang-engineering.com" <wsa-dev@sang-engineering.com>
To: Hamish Martin <Hamish.Martin@alliedtelesis.co.nz>
Cc: "mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"andi.shyti@kernel.org" <andi.shyti@kernel.org>,
"naresh.kamboju@linaro.org" <naresh.kamboju@linaro.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"lkp@intel.com" <lkp@intel.com>, "arnd@arndb.de" <arnd@arndb.de>,
linux-i2c@vger.kernel.org
Subject: Re: [linux-next:master 11602/11963] ERROR: modpost: "acpi_device_notify_remove" [drivers/i2c/i2c-core.ko] undefined!
Date: Thu, 7 Mar 2024 09:21:29 +0100 [thread overview]
Message-ID: <Zel5CYKpg82mErNQ@shikoro> (raw)
In-Reply-To: <6da20a8cf84d358841068e7eff3323b6d61e014b.camel@alliedtelesis.co.nz>
[-- Attachment #1: Type: text/plain, Size: 310 bytes --]
> My recent change introduced a build failure when building as a module.
I will revert this change to remove problems in linux-next. It does not
make sense to push a fix together with an incremental fix that late in
the cycle anyhow. Please resend the updated patch as a whole. I'll try
to get it into 6.8.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-03-07 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 13:15 [linux-next:master 11602/11963] ERROR: modpost: "acpi_device_notify_remove" [drivers/i2c/i2c-core.ko] undefined! kernel test robot
2024-03-05 22:27 ` Hamish Martin
2024-03-05 22:35 ` wsa-dev
2024-03-07 8:21 ` wsa-dev [this message]
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=Zel5CYKpg82mErNQ@shikoro \
--to=wsa-dev@sang-engineering.com \
--cc=Hamish.Martin@alliedtelesis.co.nz \
--cc=andi.shyti@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mika.westerberg@linux.intel.com \
--cc=naresh.kamboju@linaro.org \
--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 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.