lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMuHMdWvDEt3EEQj=KfVJhzT2y50ozNUQE_PpLP3QpzvRwGpLA@mail.gmail.com>
Date:   Wed, 19 Jul 2023 12:20:20 +0200
From:   Geert Uytterhoeven <geert@...ux-m68k.org>
To:     Uwe Kleine-König 
        <u.kleine-koenig@...gutronix.de>
Cc:     Thierry Reding <thierry.reding@...il.com>,
        Randy Dunlap <rd.dunlab@...il.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        linux-pwm@...r.kernel.org, Biju Das <biju.das.jz@...renesas.com>
Subject: Re: [PATCH v2] pwm: fix pwm-rz-mtu3.c build errors

Hi Uwe,

On Wed, Jul 19, 2023 at 12:13 PM Uwe Kleine-König
<u.kleine-koenig@...gutronix.de> wrote:
> On Wed, Jul 19, 2023 at 09:40:22AM +0200, Thierry Reding wrote:
> > On Tue, Jul 18, 2023 at 06:57:16PM +0200, Uwe Kleine-König wrote:
> > > On Tue, Jul 18, 2023 at 03:24:58PM +0200, Thierry Reding wrote:
> > > > Honestly, do we really need all of this complexity? I have specific
> > > > configurations to test all of the PWM drivers to make sure they build.
> > > > There's probably edge cases that don't get tested, but sooner or later I
> > > > expect some build bot will encounter those and then we can rectify
> > > > things. But in many cases that I've seen COMPILE_TEST just happens to do
> > > > more harm than good.
> > >
> > > Without COMPILE_TEST you'd need to build at least for the following
> > > archs to build all pwm drivers:
> > >
> > >     armv4+5
> > >     armv7
> > >     armv7m
> > >     arm64
> > >     mips
> > >     riscv
> > >     shmobile
> >
> > This one is actually ARCH_RENESAS and is armv7.
>
> Oh indeed. ARCH_RENESAS exists for both arm and shmobile. TIL

No, SH-Mobile can be either sh, arm, or both ;-)

ARCH_SHMOBILE is sh.
ARCH_RENESAS is arm, arm64, or riscv.

The Renesas/arm defconfig is called shmobile_defconfig for
historical reasons.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ