From: Sam James <sam@gentoo.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "H. Nikolaus Schaller" <hns@goldelico.com>,
linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Discussions about the Letux Kernel
<letux-kernel@openphoenux.org>
Subject: Re: [BUG] Add missing <linux/string.h> include for strcmp.
Date: Mon, 28 Nov 2022 21:27:04 +0000 [thread overview]
Message-ID: <06233B0E-53AC-4499-ABF0-8CD8B718278B@gentoo.org> (raw)
In-Reply-To: <20221128132507.98fab35cba20ce3f81810fcc@linux-foundation.org>
> On 28 Nov 2022, at 21:25, Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Mon, 28 Nov 2022 18:15:55 +0100 "H. Nikolaus Schaller" <hns@goldelico.com> wrote:
>
>> starting with v6.1-rc7 I can't build my tree any more:
>>
>> HOSTCC scripts/mod/modpost.o - due to target missing
>> In file included from include/linux/string.h:5,
>> from scripts/mod/../../include/linux/license.h:5,
>> from scripts/mod/modpost.c:24:
>> include/linux/compiler.h:246:10: fatal error: asm/rwonce.h: No such file or directory
>> 246 | #include <asm/rwonce.h>
>> | ^~~~~~~~~~~~~~
>> compilation terminated.
>>
>> Bisect did show your patch as the first bad one:
>>
>> commit 50c697215a8c "Add missing <linux/string.h> include for strcmp."
>>
>> Reverting it makes compile succeed.
>
> Thanks. I queued a reversion patch.
Thanks, I can't look into it properly right now so this is the best course of action. I'll test cross and the like then submit a fixed one in a few days.
next prev parent reply other threads:[~2022-11-28 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 17:15 [BUG] Add missing <linux/string.h> include for strcmp H. Nikolaus Schaller
2022-11-28 21:25 ` Andrew Morton
2022-11-28 21:27 ` Sam James [this message]
2023-02-01 23:37 Sam James
2023-02-02 8:55 ` H. Nikolaus Schaller
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=06233B0E-53AC-4499-ABF0-8CD8B718278B@gentoo.org \
--to=sam@gentoo.org \
--cc=akpm@linux-foundation.org \
--cc=hns@goldelico.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@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).