From: Arnd Bergmann <arnd@arndb.de>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: Ard Biesheuvel <ardb@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Tony Lindgren <tony@atomide.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
Stephen Boyd <sboyd@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: am335x: 5.18.x: system stalling
Date: Sat, 28 May 2022 15:13:50 +0200 [thread overview]
Message-ID: <CAK8P3a2VV26MhWz95OwfKz+2k35ee8V876iqdJdZ4o1HuNba8A@mail.gmail.com> (raw)
In-Reply-To: <CAGm1_ksndacPPpyZknvHip=7Fv+3NxXjyfCm_DDMm4EbcBuBig@mail.gmail.com>
On Sat, May 28, 2022 at 3:01 PM Yegor Yefremov
<yegorslists@googlemail.com> wrote:
> On Sat, May 28, 2022 at 11:07 AM Ard Biesheuvel <ardb@kernel.org> wrote:
> In file included from ./include/linux/irqflags.h:17,
> from ./arch/arm/include/asm/bitops.h:28,
> from ./include/linux/bitops.h:33,
> from ./include/linux/log2.h:12,
> from kernel/bounds.c:13:
> ./arch/arm/include/asm/percpu.h: In function ‘__my_cpu_offset’:
> ./arch/arm/include/asm/percpu.h:32:9: error: ‘__per_cpu_offset’
> undeclared (first use in this function); did you mean
> ‘__my_cpu_offset’?
> 32 | return __per_cpu_offset[0];
> | ^~~~~~~~~~~~~~~~
> | __my_cpu_offset
> ./arch/arm/include/asm/percpu.h:32:9: note: each undeclared identifier
> is reported only once for each function it appears in
I think you just missed the line in my patch that adds the
"extern unsigned long __per_cpu_offset[];" variable declaration.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: Ard Biesheuvel <ardb@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Tony Lindgren <tony@atomide.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
Stephen Boyd <sboyd@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: am335x: 5.18.x: system stalling
Date: Sat, 28 May 2022 15:13:50 +0200 [thread overview]
Message-ID: <CAK8P3a2VV26MhWz95OwfKz+2k35ee8V876iqdJdZ4o1HuNba8A@mail.gmail.com> (raw)
In-Reply-To: <CAGm1_ksndacPPpyZknvHip=7Fv+3NxXjyfCm_DDMm4EbcBuBig@mail.gmail.com>
On Sat, May 28, 2022 at 3:01 PM Yegor Yefremov
<yegorslists@googlemail.com> wrote:
> On Sat, May 28, 2022 at 11:07 AM Ard Biesheuvel <ardb@kernel.org> wrote:
> In file included from ./include/linux/irqflags.h:17,
> from ./arch/arm/include/asm/bitops.h:28,
> from ./include/linux/bitops.h:33,
> from ./include/linux/log2.h:12,
> from kernel/bounds.c:13:
> ./arch/arm/include/asm/percpu.h: In function ‘__my_cpu_offset’:
> ./arch/arm/include/asm/percpu.h:32:9: error: ‘__per_cpu_offset’
> undeclared (first use in this function); did you mean
> ‘__my_cpu_offset’?
> 32 | return __per_cpu_offset[0];
> | ^~~~~~~~~~~~~~~~
> | __my_cpu_offset
> ./arch/arm/include/asm/percpu.h:32:9: note: each undeclared identifier
> is reported only once for each function it appears in
I think you just missed the line in my patch that adds the
"extern unsigned long __per_cpu_offset[];" variable declaration.
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:[~2022-05-28 13:14 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 10:35 am335x: 5.18.x: system stalling Yegor Yefremov
2022-05-05 5:08 ` Tony Lindgren
2022-05-11 14:16 ` Yegor Yefremov
2022-05-12 5:41 ` Tony Lindgren
2022-05-12 5:41 ` Tony Lindgren
2022-05-12 8:14 ` Arnd Bergmann
2022-05-12 8:14 ` Arnd Bergmann
2022-05-12 8:42 ` Arnd Bergmann
2022-05-12 8:42 ` Arnd Bergmann
2022-05-12 10:20 ` Yegor Yefremov
2022-05-12 10:20 ` Yegor Yefremov
2022-05-19 16:52 ` Yegor Yefremov
2022-05-19 16:52 ` Yegor Yefremov
2022-05-21 19:41 ` Arnd Bergmann
2022-05-21 19:41 ` Arnd Bergmann
2022-05-24 13:38 ` Yegor Yefremov
2022-05-24 13:38 ` Yegor Yefremov
2022-05-24 14:19 ` Tony Lindgren
2022-05-24 14:19 ` Tony Lindgren
2022-05-26 5:49 ` Yegor Yefremov
2022-05-26 5:49 ` Yegor Yefremov
2022-05-26 6:20 ` Tony Lindgren
2022-05-26 6:20 ` Tony Lindgren
2022-05-26 8:19 ` Ard Biesheuvel
2022-05-26 8:19 ` Ard Biesheuvel
2022-05-26 12:37 ` Yegor Yefremov
2022-05-26 12:37 ` Yegor Yefremov
2022-05-26 14:15 ` Arnd Bergmann
2022-05-26 14:15 ` Arnd Bergmann
2022-05-27 4:44 ` Yegor Yefremov
2022-05-27 4:44 ` Yegor Yefremov
2022-05-27 6:38 ` Arnd Bergmann
2022-05-27 6:38 ` Arnd Bergmann
2022-05-27 6:50 ` Tony Lindgren
2022-05-27 6:50 ` Tony Lindgren
2022-05-27 6:57 ` Arnd Bergmann
2022-05-27 6:57 ` Arnd Bergmann
2022-05-27 8:17 ` Yegor Yefremov
2022-05-27 8:17 ` Yegor Yefremov
2022-05-27 8:38 ` Arnd Bergmann
2022-05-27 8:38 ` Arnd Bergmann
2022-05-27 9:50 ` Yegor Yefremov
2022-05-27 9:50 ` Yegor Yefremov
2022-05-27 12:53 ` Arnd Bergmann
2022-05-27 12:53 ` Arnd Bergmann
2022-05-27 13:12 ` Ard Biesheuvel
2022-05-27 13:12 ` Ard Biesheuvel
2022-05-27 14:12 ` Arnd Bergmann
2022-05-27 14:12 ` Arnd Bergmann
2022-05-28 5:48 ` Yegor Yefremov
2022-05-28 5:48 ` Yegor Yefremov
2022-05-28 7:53 ` Arnd Bergmann
2022-05-28 7:53 ` Arnd Bergmann
2022-05-28 8:29 ` Yegor Yefremov
2022-05-28 8:29 ` Yegor Yefremov
2022-05-28 9:07 ` Ard Biesheuvel
2022-05-28 9:07 ` Ard Biesheuvel
2022-05-28 13:01 ` Yegor Yefremov
2022-05-28 13:01 ` Yegor Yefremov
2022-05-28 13:13 ` Arnd Bergmann [this message]
2022-05-28 13:13 ` Arnd Bergmann
2022-05-28 19:28 ` Yegor Yefremov
2022-05-28 19:28 ` Yegor Yefremov
2022-05-30 10:16 ` Ard Biesheuvel
2022-05-30 10:16 ` Ard Biesheuvel
2022-05-30 12:09 ` Yegor Yefremov
2022-05-30 12:09 ` Yegor Yefremov
2022-05-30 13:54 ` Arnd Bergmann
2022-05-30 13:54 ` Arnd Bergmann
2022-05-30 15:14 ` Ard Biesheuvel
2022-05-30 15:14 ` Ard Biesheuvel
2022-05-31 8:36 ` Yegor Yefremov
2022-05-31 8:36 ` Yegor Yefremov
2022-05-31 14:16 ` Yegor Yefremov
2022-05-31 14:16 ` Yegor Yefremov
2022-05-31 15:22 ` Arnd Bergmann
2022-05-31 15:22 ` Arnd Bergmann
2022-06-01 7:36 ` Yegor Yefremov
2022-06-01 7:36 ` Yegor Yefremov
2022-06-01 7:59 ` Arnd Bergmann
2022-06-01 7:59 ` Arnd Bergmann
2022-06-01 8:08 ` Ard Biesheuvel
2022-06-01 8:08 ` Ard Biesheuvel
2022-06-01 9:27 ` Ard Biesheuvel
2022-06-01 9:27 ` Ard Biesheuvel
2022-06-01 10:03 ` Yegor Yefremov
2022-06-01 10:03 ` Yegor Yefremov
2022-06-01 10:06 ` Ard Biesheuvel
2022-06-01 10:06 ` Ard Biesheuvel
2022-06-01 10:46 ` Yegor Yefremov
2022-06-01 10:46 ` Yegor Yefremov
2022-06-01 10:49 ` Ard Biesheuvel
2022-06-01 10:49 ` Ard Biesheuvel
2022-06-02 10:17 ` Yegor Yefremov
2022-06-02 10:17 ` Yegor Yefremov
2022-06-02 10:37 ` Ard Biesheuvel
2022-06-02 10:37 ` Ard Biesheuvel
2022-06-02 12:27 ` Yegor Yefremov
2022-06-02 12:27 ` Yegor Yefremov
2022-06-03 8:54 ` Yegor Yefremov
2022-06-03 8:54 ` Yegor Yefremov
2022-06-03 9:32 ` Arnd Bergmann
2022-06-03 9:32 ` Arnd Bergmann
2022-06-03 19:11 ` Yegor Yefremov
2022-06-03 19:11 ` Yegor Yefremov
2022-06-03 20:46 ` Arnd Bergmann
2022-06-03 20:46 ` Arnd Bergmann
2022-06-05 14:59 ` Ard Biesheuvel
2022-06-05 14:59 ` Ard Biesheuvel
2022-06-07 8:55 ` Yegor Yefremov
2022-06-07 8:55 ` Yegor Yefremov
2022-08-12 7:35 ` Arnd Bergmann
2022-08-12 7:35 ` Arnd Bergmann
2022-05-24 14:36 ` Arnd Bergmann
2022-05-24 14:36 ` Arnd Bergmann
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=CAK8P3a2VV26MhWz95OwfKz+2k35ee8V876iqdJdZ4o1HuNba8A@mail.gmail.com \
--to=arnd@arndb.de \
--cc=ardb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tony@atomide.com \
--cc=yegorslists@googlemail.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 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.