From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: Basavaraj Natikar <basavaraj.natikar@amd.com>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: build failure of next-20220728 due to 93ce5e0231d7 ("HID: amd_sfh: Implement SFH1.1 functionality")
Date: Thu, 28 Jul 2022 18:17:49 +0100 [thread overview]
Message-ID: <YuLEvUKxrcwe2dZp@debian> (raw)
Hi All,
Not sure if it has been reported, builds of xtensa, mips, csky and arm allmodsconfig
have failed to build next-20220728 with the error:
drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_interface.c: In function 'amd_stop_sensor':
drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_interface.c:48:9: error: implicit declaration of function 'writeq'; did you mean 'writel'? [-Werror=implicit-function-declaration]
--
Regards
Sudip
next reply other threads:[~2022-07-28 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 17:17 Sudip Mukherjee (Codethink) [this message]
2022-07-28 17:24 ` build failure of next-20220728 due to 93ce5e0231d7 ("HID: amd_sfh: Implement SFH1.1 functionality") Basavaraj Natikar
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=YuLEvUKxrcwe2dZp@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=basavaraj.natikar@amd.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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).